Archon
coleam00/Archon β workflow engine for AI coding agents. You define the development process as a YAML workflow (plan β implement β validate β review β PR) and run it deterministically via CLI, Web UI, Slack, Telegram or GitHub. README analogy: Dockerfile did this for infrastructure, GitHub Actions for CI/CD β Archon does this for AI coding.
Itβs a direct response to the problem described in Karpathy Skills and Harness Engineering: without a structural frame, every LLM run produces a different result. Archon freezes the structure (deterministic nodes) and leaves intelligence at the points where it actually adds value (AI nodes).
π Links
Description
- Repo: https://github.com/coleam00/Archon
- Docs: https://archon.diy/
- Book of Archon (10-chapter tutorial): https://archon.diy/book/
- License: MIT
Download or use
# Full setup (5 min) β wizard, web UI, skill copy
git clone https://github.com/coleam00/Archon
cd Archon && bun install && claude
# Then say: "Set up Archon"
# Quick install β CLI binary only (requires a separate Claude Code)
curl -fsSL https://archon.diy/install | bash # macOS/Linux
irm https://archon.diy/install.ps1 | iex # Windows PS
brew install coleam00/archon/archon # HomebrewWorkflows live in .archon/workflows/*.yaml, commands in .archon/commands/*.md β committed to the repo so the whole team uses the same process.
ποΈ Description
π§© What Archon actually does
A workflow is a DAG of nodes, where each node is either:
- Deterministic β
bash:(tests, git ops, custom scripts), never fires AI - AI β
prompt:with optionalloop: until: ...andfresh_context: true(fresh session per iteration) - Interactive β
loop: until: APPROVEDwithinteractive: true(pauses for human review)
Each run gets its own git worktree β you can run 5 fixes in parallel without conflicts. Fire and forget β come back to a finished PR.
π§© Example workflow
# .archon/workflows/build-feature.yaml
nodes:
- id: plan
prompt: "Explore the codebase and create an implementation plan"
- id: implement
depends_on: [plan]
loop:
prompt: "Read the plan. Implement the next task. Run validation."
until: ALL_TASKS_COMPLETE
fresh_context: true
- id: run-tests
depends_on: [implement]
bash: "bun run validate"
- id: review
depends_on: [run-tests]
prompt: "Review all changes against the plan. Fix any issues."
- id: approve
depends_on: [review]
loop:
prompt: "Present the changes for review. Address any feedback."
until: APPROVED
interactive: true
- id: create-pr
depends_on: [approve]
prompt: "Push changes and create a pull request"π§© Bundled workflows (17 total)
| Workflow | Use case |
|---|---|
archon-assist | General Q&A, debugging β full Claude Code with tools |
archon-fix-github-issue | Issue β classify β plan β implement β PR β self-fix |
archon-idea-to-pr | Idea β plan β implement β 5 parallel reviews β self-fix |
archon-plan-to-pr | Execute an existing plan β implement β PR β review |
archon-comprehensive-pr-review | 5 parallel reviewers + auto-fix |
archon-resolve-conflicts | Detect β analyze both sides β resolve β validate β commit |
archon-architect | Architectural sweep, complexity reduction |
archon-refactor-safely | Refactor with type-check hooks and behavior verification |
archon-ralph-dag | PRD implementation loop β walk through stories to completion |
archon workflow list shows them all. Same-named files in your repo override bundled defaults.
π§© Architecture
Platform Adapters (Web UI, CLI, Telegram, Slack, Discord, GitHub)
β
Orchestrator
(routing + context)
β β β
Command Handler Workflow Executor AI Assistant Clients
(slash) (YAML DAG) (Claude / Codex / Pi)
β
SQLite / PostgreSQL (7 tables:
codebases, conversations, sessions,
workflow runs, isolation envs, messages, events)
The Web UI has a separate mission-control dashboard, drag-and-drop workflow builder, step-by-step execution view and aggregates conversations from all platforms in one place.
βοΈ Reasoning for
From my perspective this is exactly the layer thatβs missing between Claude Code and a repeatable dev workflow in Qamera AI and PLSoft. Today I treat every issue as if it were the first β with Archon I can define once βthis is how I fix issues in this repoβ and then Use archon to fix issue #42 gives me a predictable PR.
Three things especially worth considering:
- Worktree isolation β eliminates the βAI agent broke my branchβ problem (I hit this almost weekly)
- Fire-and-forget via Telegram/Slack β fire a workflow from my phone, come back to a finished PR
- Fresh context per iteration in loop nodes β the opposite of long Claude Code sessions where context gets poisoned after 30+ tool calls
Weak spot: 17 bundled workflows is a lot of abstraction to learn. Iβll probably start with archon-fix-github-issue and archon-idea-to-pr, and pick up the rest as I need them.
Alternatives considered
- Claude Code on its own β no structural gates, no deterministic nodes, every run is different
- Awesome Claude Code β curation of skills/prompts, not a workflow engine
- GitHub Actions + Claude Code β works, but no worktree isolation and no AI loop nodes with fresh context
- n8n / Zapier β workflow engines, but not designed for git/coding context
π Resources
- Author X: https://x.com/coleam00
- Telemetry opt-out:
ARCHON_TELEMETRY_DISABLED=1orDO_NOT_TRACK=1 - Previous v1 (Python, task management + RAG): branch
archive/v1-task-management-rag
Template: tool