Start
Install, scaffold a configuration, run doctor, and open your first Session. Begin →
Axocoatl documentation
One durable Session. The whole workspace around it.
Axocoatl is a local-first coding workbench backed by a durable Rust agent runtime. A folder-anchored Session keeps conversation, context, files, terminal, Preview, tools, history, and Git review together. Start with the Agent or configured team that fits the work. Explore several Ways only when the task warrants comparison.
The shortest path
Section titled “The shortest path”- Install the binary.
- Run
axocoatl onboardandaxocoatl doctor. - Start
axocoatl dev, openhttp://localhost:8080, and create a Session. - Ask for a bounded change, review what happened, run the repository checks, and inspect Git.
Pick the task in front of you
Section titled “Pick the task in front of you”Use the workbench
Work in Conversation, open Files, Terminal, Preview, History, and Git, and use several Ways when one answer is not enough. Open the guide →
Configure
Set providers, Agents, sandboxes, Skills, MCP servers, and Automations. Configure Axocoatl →
Operate
Run the service, back up local state, upgrade deliberately, and diagnose failures. Operations guide →
Understand
Learn the ownership boundaries behind Sessions, attempts, memory, events, and protocols. Read the model →
Reference
Look up CLI commands, configuration fields, HTTP routes, WebSocket frames, and examples. Open reference →
What stays local—and what may not
Section titled “What stays local—and what may not”The daemon and default Podman sandbox run on your machine, and Axocoatl adds no product telemetry. That does not mean every configured path is offline. Hosted model providers, remote MCP servers, web search, webhooks, bridged sandbox networking, embedding-model downloads, and an E2B Cloud remote sandbox can send data over the network. Review the security boundary before using untrusted input →