Archon is a workflow engine for AI coding agents. Instead of hoping an AI agent remembers to plan, test, and write a proper PR description, you encode that process as a YAML workflow with defined phases and validation gates. The AI fills in the intelligence at each step, but the sequence of actions stays the same every run. It's built for developers who use Claude Code (or similar coding agents) and want repeatable, auditable automation instead of ad-hoc prompting.
The project compares itself to Dockerfiles for infrastructure or GitHub Actions for CI/CD, applied to AI-assisted development. Workflows live in .archon/workflows/, get committed to your repo, and run the same way from the CLI, a web dashboard, Slack, Telegram, or GitHub.
depends_on relationships and loops.interactive: true loop nodes pause execution and wait for a person to approve or give feedback before continuing.ALL_TASKS_COMPLETE is met.~/.archon/workflows/, with project-level files overriding bundled defaults.Archon fits teams and solo developers who already use an AI coding agent (Claude Code, with Codex and Pi also supported) and are frustrated by inconsistent results: sometimes the agent tests, sometimes it doesn't, sometimes the PR description follows the template and sometimes it doesn't. If you want "fix this bug" or "add this feature" to always follow the same plan-implement-validate-review-PR sequence, this is built for that.
It also works well if you want to fire off multiple parallel tasks (each isolated in its own git worktree) and come back later to finished PRs with review comments already applied. Teams that want a shared, versioned definition of "how we do code review" or "how we resolve merge conflicts" can commit those workflows to the repo so everyone's agent follows the same process.
It's not a good fit if you just want quick, single-shot AI code suggestions with no process around them, or if you're not using a coding agent that Archon can drive (currently Claude Code, Codex, and Pi). Teams without CI/test setups to validate against will get less value from the validation-gate parts of workflows, since there's less for the deterministic nodes to check.
Archon runs on Bun and integrates with Claude Code. The full setup wizard handles credentials, platform integrations, and copies the Archon skill into your target projects:
git clone https://github.com/coleam00/Archon
cd Archon
bun install
claude
Then tell Claude Code: "Set up Archon" and follow the wizard.
If you already have Claude Code installed and just want the CLI, use the quick install instead:
# macOS / Linux
curl -fsSL https://archon.diy/install | bash
# Windows (PowerShell)
irm https://archon.diy/install.ps1 | iex
# Homebrew
brew install coleam00/archon/archon
Compiled binaries don't bundle Claude Code; install it separately and set CLAUDE_BIN_PATH to point Archon at it, or set assistants.claude.claudeBinaryPath in ~/.archon/config.yaml.
Once set up, run Claude Code from your target project (not from the Archon repo) and invoke workflows directly:
cd /path/to/your/project
claude
Use archon to fix issue #42
For the web dashboard, binary installs can run archon serve; from source, run bun run dev from the Archon repo root.