Milestones
List view
Pi extension bridge (untether-pi-bridge) — interactive permissions via the RPC dialog channel landed in v0.35.8. Ships a small TypeScript pi extension (~100 LOC) auto-installed on first Pi run. From the Pi enhancement plan at docs/plans/2026-05-02-pi-engine-enhancements.md (Tier 4).
No due date•0/1 issues closedPi RPC mode runner — opt-in `[pi] runner = "rpc"` with USD cost via get_session_stats. Foundation for #180 (extension bridge in v0.35.9). Defaults preserve current --mode json runner. From the Pi enhancement plan at docs/plans/2026-05-02-pi-engine-enhancements.md (Tier 3).
No due date•0/1 issues closedLong-tail security hardening: dependency hygiene, observability, pre-flight cost gating, bot-token rotation. Follow-up to v0.35.6.
No due date•0/13 issues closedSecurity hardening follow-ups surfaced by the 2026-04-20 agent-orchestration audit (docs/audits/agent-orchestration-security-audit-2026-04-20.md). Not release-critical, but should not drift past one quarter.
No due date•0/16 issues closedPer-trigger permission overrides (all engines + webhooks). Research-heavy — security review and per-engine audit across all six engines. Depends on #170-#174 prerequisite work for full coverage, and on completing partial permission_mode wiring in Codex/Gemini.
No due date•2/79 issues closedEngine-lineup turnover. REMOVE the deprecated gemini and amp engines (deprecated in 0.35.5) plus the AMP-only /threads command. INTRODUCE the new Antigravity CLI (agy) engine as Gemini CLI's successor (#558) — a distinct engine, NOT a gemini rename: it must not reuse the gemini engine id, because auth, CLI flags and session semantics all differ. Also lands EngineBackend.status/deprecated on the backend registry, replacing the DEPRECATED_ENGINES id set added in 0.35.5 — needed to render a supported antigravity alongside a retired gemini. PREREQUISITE: removal breaks three observable interfaces (accepted config values, built-in entry points, the /threads command), which .claude/rules/release-discipline.md reserves for major. This milestone requires first amending that policy to allow announced breaking removals in 0.x minors after one deprecation release. Retired engine ids must fail closed — never silently reroute a run to a different provider.
No due date•0/3 issues closedAcknowledged ideas and investigations — not yet scheduled.
No due date•1/24 issues closed