Projects

claude-autodev — Autonomous 8-Stage Dev Pipeline for Claude Code

Active
Node.js 22+ESMSQLiteHTTP + Server-Sent Eventsgit worktreesClaude Code CLIgh CLInode:test
Product demo

Problem

Agentic coding tools stop at a diff. Nothing forces a spec to exist before implementation, nothing blocks a run that never wrote a test, and nothing catches a stage that quietly produced no artifact — so failures surface as a plausible-looking PR nobody can trust.

Business Impact

The gap between an AI-written diff and shippable software is spec, review, and test discipline — exactly the parts teams skip when the agent looks confident. claude-autodev makes those parts mandatory gates, so an unattended run either produces a reviewed, tested PR or stops with a diagnosis instead of a false green.

System Approach

  • Eight stages, each a fresh headless claude -p session with zero shared context between them
  • Artifact gates per stage — no artifact, no advance
  • Isolated git worktree per run so concurrent runs never collide
  • SQLite registry plus per-run events.jsonl as source of truth; HTTP+SSE server drives the dashboard read-only
  • Bounded retries with self-fix, then park BLOCKED with a written diagnosis
  • Daemon mode turns tracker issues into runs and issue labels into the queue

Key Decisions & Trade-offs

  • No shared context between stages — an independent reviewer is worth more than a cheaper one
  • Gate on artifacts, not on the model saying it finished
  • Worktree isolation over branch switching so a stuck run never blocks the main checkout
  • Server is a viewer, not a dependency — the pipeline completes with the dashboard closed
  • Deploy stage is opt-in; merging and shipping should never be an accident

Current Status

Public and open source (MIT) at v0.2.0. Test suite runs on Linux, macOS, and Windows across Node 22 and 24 in CI on every push. Ships autodev selftest, which drives a fixture repo through all seven stages in about 30 seconds without spending model quota, and autodev doctor for preflight checks with a fix per failure.

Roadmap

  • Multi-repo runs so one requirement can span services
  • Pluggable review policies per repository
  • Cost and duration budgets per run with hard stop

What I'd Improve Next

  • Hosted dashboard mode for teams watching several runs at once
  • Richer holdout scenario authoring so the test gate is harder to game

Explore More