Milestones
List view
Planned usability and observability release: clipboard-image retention/cleanup, running-command detail, pet qualification, Fleet save-in-role/model presentation, usage/tool diagnostics, per-call cache views and clickable file previews. Undated planning target approved November 5, 2026. Scope and data-loss semantics must be resolved before implementation; preserve accessibility, explicit cleanup controls and authoritative accounting. This milestone does not create a published release.
No due date•0/7 issues closedPlanned follow-up: reliability hardening, replay/archive retention, cache-economics evidence, native CPU/IME investigation and bounded dead-code cleanup. Undated planning target approved November 5, 2026, not a published release or a completion claim. Revalidate historical audit candidates against current source before implementing. Any confirmed defect that blocks the agreed 0.10.3 release must be promoted back immediately; this milestone is not a security or data-integrity waiver. Preserve recovery before applying retention limits, and obtain approval for paid-provider experiments.
No due date•0/21 issues closedGood places to contribute: scoped issues a contributor can pick up without maintainer-only access. Comment on the issue to claim it, and see CONTRIBUTING.md. Release blockers live in the version milestones.
No due date•0/1 issues closedCorrective release and exact-candidate qualification. Release scope approved November 5, 2026. Keep history/undo and compaction continuity, login/model selection, worker durability and safe retries, bounded input/output, runtime responsiveness, and supported installation/client qualification here. Use release-blocker for the unresolved repair/qualification gates. Use status:awaiting-release for source fixes that are landed but still need final verification and shipment; do not close them merely because main contains the fix. Broad refactors, optional features, full historical audit sweeps and unqualified optimization claims move to the later planning milestones. This replaces the previous all-refactors-for-0.10.3 umbrella scope; unfinished requirements are deferred, not completed or discarded. Confirmed release-critical defects must not be hidden by a future umbrella target. Freeze the final source and binaries, finish the required platform/client evidence, then run final validation. Provider spend, signing and publication retain their separate approvals. No due date or published release is created by this milestone.
No due date•37/46 issues closedPlanned architecture release. Reuse this existing milestone rather than creating a competing v0.11.0 bucket. Scope approved November 5, 2026: gix read-path adoption, coarse host/crate decomposition, completion of the command-contract frontier, typed Responses profiles and tool projection, embedder capability contracts, incremental context-folding/model-invoked compaction, and optional independent goal verification. Complete every admitted consumer of a migration, retain a single turn loop/request authority, and qualify platform, cancellation and recovery behavior. Existing PRs and historical completed work stay attached. No due date or publication commitment.
No due date•44/56 issues closedKept ideas without a release commitment: platform requests, integrations and speculative features. Say why when you pick one up or close it; nothing here blocks a release.
No due date•73/77 issues closedLonger-term product planning: full cross-platform desktop completion, an explicitly designed pluggable-memory contract, and user-approved automatic skill learning/evolution. Release routing refreshed November 5, 2026. Memory/learning items remain design work with privacy and approval requirements, not implemented capabilities. Provider/command/context architecture is tracked in the existing v0.11 milestone; speculative platform/integration requests stay in Backlog. Existing completed work is retained. Undated, not a publication commitment.
No due date•36/39 issues closed