Progress
The public roadmap describes progress by feature. This page is the engineering view: one complete 1.0, delivered through twelve milestones. A milestone has two states worth separating. Implemented means its code is merged on the main branch with tests. Closed means its acceptance checklist, the gate, has passed on macOS, Windows and Linux. A milestone can be implemented with its gate still open, and the notes say when that is the case. A screen existing is not a feature existing.
Automated checks ran on all three platforms during the first milestone (October 2026). They are paused at the moment, so work merged since then has been verified by hand on macOS only.
Reconciled with the desktop project on 2026-10-19. Implemented in development means the feature works in the current source on macOS and is not in any public release. Windows and Linux are not yet verified by hand.
| Milestone | Scope | Status |
|---|---|---|
| M1 Architecture, security and foundation | Documented contracts, threat model, monorepo, Tauri shell, Rust crates, settings store, SQLite, policy engine and test scaffolding.The code is merged and passed automated checks on macOS, Windows and Linux on 2026-10-16. The milestone gate is still open on two non-code items, the design-token set and Windows/Linux performance numbers, so M1 counts as implemented but not closed. | Implemented in development |
| M2 Production terminal | PTY-backed shells, tabs and splits, shell integration, search, session restore, SSH, settings and themes.Terminal view, tabs, splits, search, theme, restore, shell integration, links, settings, SSH and PowerShell are merged. Windows shells by hand, a performance re-check and the gate script remain. | In progress |
| M3 Rust provider gateway and local AI | OS keychain credentials, direct model adapters with streaming, a capability registry, routing baseline, local runtime detection.Credentials, Anthropic, OpenAI-compatible and Gemini adapters, the provider manager, Ollama and LM Studio detection, routing profiles, budgets and usage are merged. Model downloads and coding-agent account connections are not. | In progress |
| M4 Native single-agent coding | A Rust model and tool loop with Ask, Plan, Build, Debug and Review modes, context inspection, diff approvals and session history.Agent loop, Agents view, diff approvals, project discovery, conversations, scoped memory, structured plans, the terminal tool and the egress preview are merged. Windows and Linux verification remains. | In progress |
| M5 Workspaces, Git and editor | Repository management, Git views, worktrees, project state, search and indexing, the editor and snapshots.Git core and view, branches, worktrees and stashes through your installed git, project state, the Board foundation, snapshots and the Code view (Monaco bundled locally, explorer under ignore rules, search, conflict-detecting saves, diff against HEAD) are merged. Language servers, push and pull, a search index and remote editing are not started. | In progress |
| M6 Native Factory orchestration | Task DAG, manager and worker roles, leases, scheduling, isolated teams, Council orchestration and the Agent Inbox.Plan materialisation, leased task runs, Council orchestration, the manager and worker hierarchy and the Agent Inbox are merged. | In progress |
| M7 Verification, recovery and integration | An independent verifier, bounded repair loops, snapshots with restore, and an integration pipeline with evidence reports.Independent verification, the integrator with conflict preview and approval, and snapshots are merged. | In progress |
| M8 Control plane, workers and agent APIs | A durable background daemon, first-party remote workers, service registry, typed versioned APIs and headless multi-project control. | Planned |
| M9 Routing, budgets, workflow and event engine | Policy inheritance, model pools and fallbacks, cost dashboards, a scheduler, standing orders, event and webhook triggers, and a workflow builder. | Planned |
| M10 Extensibility | Extension API and host, MCP client and server, permissions, contribution docs, Linear, Jira, Asana, GitHub and GitLab adapters for the Board. | Planned |
| M11 Design, platform and operational polish | Full visual consistency, keyboard and accessibility work, onboarding, settings, platform quirks and performance targets. | Planned |
| M12 Hardening and public release | Security review, red-team tests, regression suite, crash and recovery drills, signed installers, updates and release-candidate acceptance. | Planned |
Dependency order
Section titled “Dependency order”M1 first. M2 (terminal), M3 (providers) and M5 (workspaces, Git, editor) can proceed in parallel after it. M4 (single-agent coding) needs M3. M6 (Factory) needs M4 and M5. M7 (verification and integration) needs M6. M8 (control plane, workers, APIs) and M9 (routing, budgets, scheduling) need M7. M10 (extensibility and MCP) needs M8 and M9. M11 (polish) needs everything functional, and M12 (hardening and release) needs M11.
Release gates
Section titled “Release gates”Twelve demonstrations must pass with recorded evidence before 1.0: terminal offline; a direct API model; a local model offline; plan, implement, verify, approve; a Factory run where an independent verifier catches a seeded defect; queue and audit surviving a restart without unsafe replay; remote worker reconnect; a user-defined agent API; a scheduled workflow with disclosed requirements; credential and data deletion; malicious repository text unable to override policy; and install, shells and update on all three operating systems.