Skip to content
Oleg Miagkov edited this page Jul 13, 2026 · 3 revisions

Auto Code — Roadmap & Status

A living set of pages: what's done · in progress · planned · strategy. Consolidates every roadmap in the project. Updated as PRs land.

Updated: 2026-07-13 · Development branch: develop · Last PR reflected: #422

Status legend: ✅ done · 🚧 in progress · ⬜ planned (not started) · 🟢 partial / milestone reached


Positioning (why all this)

The AI-coding market is growing, but the biggest unmet pain is trust in AI output. The autonomous-agent space is squeezed from above (Claude Code, Copilot agent) and below (OpenHands).

Our moat is the intersection of three things almost nobody combines:

  1. spec-driven discipline;
  2. a closed loop "autonomous execution → QA → fixes" with worktree isolation and explicit review gates;
  3. open-source + self-hosted + multi-provider (data never leaves the perimeter).

Positioning: "an autonomous coder you can trust and run on your own infrastructure," aimed at the regulated self-hosted enterprise.

Strategic link: local models (P3) + self-hosted multi-user (P4) = regulated enterprise.


Status at a glance

Roadmap Status Details
Strategic goals (P1–P5) · Wave 1 ✅ Done trust · autonomy · cost
Strategic goals (P1–P5) · Wave 2 (P2 GitHub App) ⬜ Not started ~75% of primitives reusable
Strategic goals (P1–P5) · Wave 3 (P4 cloud) 🚧 Partial libs/ui underway; backend not started
Multi-provider / CLI runner (design) 🚧 Design nearly complete phases 1–6 done; 7–8 in progress
Non-Claude provider autonomy 🚧 In active development Codex CLI is the only full-autonomous path
Language support (~20 languages) ✅ Complete PR #418
Device & GUI verification 🚧 Just started Track A (Android) started

Pages


What's next (priorities)

  1. Promote OpenAI to full-autonomous (details) — removes the Claude-SDK dependency for the autonomous path.
  2. P2 GitHub App (Wave 2) — distribution; only GitHub App auth + issues.assigned webhook are missing.
  3. Track D libs/ui (U5–U7, Wave 3) — foundation for the cloud and desktop UI.
  4. Track A Android (A2 adb tools, details) — take Android to L3/L4.
  5. Track C cloud backend (Wave 3) — the largest chunk; starts with C1.

Project rule: no time estimates. Order is by impact/effort, not calendar.


Sources (in the repo)

How to keep current: edit the relevant page whenever a roadmap-affecting PR lands; keep "Status at a glance" here in sync. A CI workflow opens a reminder issue (label wiki-sync) when roadmap docs change on develop.

Clone this wiki locally