Architecture
nax is a layered CLI around a workflow engine. The command parser stays thin, workflow files describe agent orchestration, transports submit work to Netlify Agent Runner, and local stores preserve enough state to resume, inspect, and hand off the results.
Big picture
Components
| Component | Role |
|---|---|
| CLI command layer | Parses commands and normalizes options. |
| Workflow catalog | Loads bundled and project-local flows. |
| Workflow engine | Applies model overrides, context, inputs, waits, and state. |
| Transports | Submit work through GitHub Actions or local Netlify API. |
| Prompt delivery | Combines prompts, context, prior results, and blob offload. |
| Artifacts | Persist summaries, events, sessions, runners, and workflow state. |
| Dashboard | Provides local graph, event, run detail, and follow-up UI. |
Why this shape
The important design choice is that orchestration lives in files, not terminal history. A team can review a flow.yml, inspect prompt Markdown, compare artifacts from prior runs, and rerun only the steps they need.
Non-goals
naxis not a local model runner.naxis not a general CI system.naxdoes not hide transport prerequisites.naxdoes not automatically decide that an agent recommendation is correct.
See also
- Transports for execution trade-offs.
- Artifacts for saved state and handoff paths.
- Workflow file reference for the schema that drives the engine.
- Use the dashboard for the browser surface.
Last updated on