Product Roadmap
Measured engineering milestones, current release status, and tracked technical debt.
Current Status: v0.1.0 Released
Every phase of the V3 Specification is implemented, verified, and shipped in the v0.1.0 release.
Shipped & Verified
Production Ready (v0.1.0)
- Core Subprocess Isolation:
LaunchPlancontract, Unixexec, Windows child launcher, passthrough args, exit code preservation. - Twelve Evidence-Measured Adapters: Claude Code, OpenAI Codex, Aider, Gemini CLI, GitHub Copilot, OpenCode, Cursor, Continue, Amp, Cline, Windsurf, Kiro.
- Repository Resolution: Canonical Git root discovery, symlink/junction canonicalization, worktree/submodule isolation, deterministic precedence engine.
- Mapping & Lifecycle CLI:
link,unlink,status,resolve,current,create,list,delete,repositories. - Inspection & Diagnostics: Comprehensive
doctorsubcommand, machine-readable--jsonacross all reporting commands. - Shell Ergonomics: Native tab autocompletions for Bash, Zsh, Fish, PowerShell, and Elvish.
Active Focus (v0.2.0)
In Progress
- Automated Sandbox Regression CI: Continuous containerized delta-probing on agent version upgrades.
- Mechanism Migration Tracking: Sentinel path detection in
doctorfor vendor configuration changes. - Dynamic Shell Completions: Evaluating dynamic profile-name autocompletion hooks across shells.
- Keychain & Helper Auditing: Extended diagnostic checks to identify OS keyring credential bleed.
The 6 Sub-Project Build Sequence
How the architecture was engineered under the V3 Specification:
| Subproject | Deliverable | Spec Phases | Status |
|---|---|---|---|
| SP0 | Scaffolding, workspace tooling, PolyForm licensing, test fixtures. | Setup | Done |
| SP1 | Core CLI, TOML config with locked atomic writes, LaunchPlan, process launcher. | Phase 1, 3 | Done |
| SP2 | Adapter architecture, capability metadata, Claude Code, Codex, Aider adapters. | Phase 4A | Done |
| SP3 | Repository discovery, canonical Git identity, precedence engine, link/unlink. | Phase 2, 5 | Done |
| SP4 | Remaining 9 adapters backed by containerized CI sandbox probe captures. | Phase 4B | Done |
| SP5 | Lifecycle management, repositories report, doctor, completions, documentation. | Phase 5, 6 | Done |
Tracked Technical Debt & Boundaries
Antigravity CLI has no isolation mechanism, and the evidence says so:
Measured against agy: nothing relocates ~/.gemini/antigravity-cli/, and credentials live in the OS keyring. Because Agent Profile guarantees that every adapter establishes real isolation, Antigravity CLI is not shipped as an adapter until upstream supports relocation.
Profile Names Completion:
The current shell completion scripts are intentionally static. Completing dynamic profile names from disk requires an active runtime bridge, planned for the v0.2 cycle.
Future Research: Workspace Swarms
In collaborative AI environments like Clavity (Claude Code driver + Antigravity peer), multiple agents coordinate inside the same repository. We are actively investigating ephemeral disposable profiles and cryptographic memory partitions for dual-agent pairing.