Get started
This tutorial takes a new checkout from install to a working nax dry run. It assumes you already have a GitHub repository and a Netlify project, because nax submits real repository work to Netlify Agent Runner rather than simulating agents locally.
Prerequisites: Node 20+, authenticated netlify-cli, authenticated gh, and a Git repository connected to a Netlify project.
Install nax
npm install -g @davidwells/netlify-agent-executorVerify the command:
nax --help
nax listConfirm the required CLIs are authenticated before initialization:
netlify status
gh auth statusInitialize the project
nax initTo preview setup before writing files or secrets:
nax init --dryTo use only local Netlify API orchestration:
nax init --no-github-actionsPreview a workflow
nax run review --dry --forceThe dry run loads the flow, resolves prompts, and prints the plan without creating GitHub issues, Agent Runner jobs, or .nax artifacts.
Run for real
nax run reviewForce local Netlify API orchestration when you want resume support and dashboard event streaming:
nax run review --transport netlify-apiInspect the result
nax handoff -c
nax dashboard reviewArtifact checkpoint
Completed workflows write summaries under:
.nax/workflows/<workflow-run-id>/artifacts/summary.md
.nax/agent-runners/<runner-id>/summary.md
.nax/agent-sessions/<session-id>/summary.mdCommon mistakes
A dry run intentionally does not create .nax artifacts. Use it to verify the plan, then run the workflow without --dry when you want results.
- Running before
ghornetlifyare authenticated. - Running against a branch whose pinned SHA has not been pushed.
- Rebuilding the dashboard with an older Node version.
Next steps
- Run workflows for branch targeting, model overrides, retries, and single-agent runs.
- Write custom workflows for project-local flows.
- Transports for choosing the right execution path.