You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status (2026-09-22): v0.10.0 is published. 0.10.1 is in planning. 0.10.1 is a patch release: it finishes work 0.10.0 started. It adds no new features and makes no breaking changes. This is a release plan, not a release announcement. A version bump in source does not mean packages or binaries have been published.
What shipped in 0.10.0
A redesigned terminal workbench, clearer model, provider, fleet and plugin settings, and more reliable session and runtime behavior. It replaces the unpublished 0.9.14 candidate.
The v0.10.0 milestone keeps its completion history, including the links carried over from the former v0.9.14 plan.
What 0.10.1 is: finish what we started
Each item below already has one or more partial fixes behind it. 0.10.1 closes those gaps instead of adding scope. CI and release-pipeline fixes land first, because every other change lands through that gate.
Empty terminal stop ends the turn (ACP follow-up: empty terminal responses and Full Access discovery #6310). When a model returns a clean stop with no text and no tool call, the turn should retry a bounded number of times and then fail visibly. The same handling must apply on the ACP serve path.
git_fetch can hang on a credential prompt. Tool-side git spawns should never prompt on the terminal (GIT_TERMINAL_PROMPT=0, SSH in batch mode), and fetch should run under a timeout.
Sub-agent completion events can be dropped. Terminal lifecycle events must always be delivered, so a finished sub-agent never shows as Running.
Desktop app engine version check. The app should accept any 0.10.x engine, not only exactly 0.10.0.
/context shows a different number from the meter. Make /context lead with the same estimate the meter and the auto-compact gate use.
Shipped text that contradicts shipped behavior. Fix stale /debug cache status lines, make remote-setup --apply either work or exit non-zero, and correct the glibc/GNU wording (both Linux assets are static musl).
CI and release pipeline (these land first)
Make the CI ratchets block pull requests the same way they block main, so a green PR cannot turn main red. Each ratchet gets an update command so the fix lands in the same PR.
Update the release record automatically after publish, so a new release no longer turns Web Frontend red.
Run the parity gate in the release candidate, so the tagged SHA is the SHA the candidate validated.
Keep macOS jobs on fork PRs within the 90-minute limit, and keep the Actions cache under its size cap.
Stop the PR-to-issue link check from reading "does not close #N" as a closing keyword. Automation applies labels and does not post comments.
ACP sessions on the full turn runtime (#5835), the session-store rewrite (#6144), sub-agent decomposition (#6293), the catalog single-authority work (#6396), the context_status tool (#6217), and test-environment convergence.
Where work is tracked
The v0.10.1 milestone is the release list. Items above without an issue link get one when work starts.
Issues mirror to our internal tracker automatically, so please file once.
How PRs land
Every PR lands through hosted CI. A local pass, a model trial and a published release are separate levels of evidence, and one does not stand in for another.
Contributor PRs are reviewed and merged as their own PRs, with credit. If your branch needs a rebase or a fix, we help on your branch.
Write Fixes #N or Closes #N only when the PR really resolves the issue. Otherwise use Refs #N.
How to report
Bugs: use the bug report template. Include reproduction steps, codew --version (with the build SHA), and the client and operating system you used. For a freeze, say what the turn was doing when it stopped, and attach anything that appeared in crashes/.
Design feedback: show the screen and describe what you were trying to do, what was unclear, and your window size. Mouse and keyboard behavior both matter.
Status (2026-09-22): v0.10.0 is published. 0.10.1 is in planning. 0.10.1 is a patch release: it finishes work 0.10.0 started. It adds no new features and makes no breaking changes. This is a release plan, not a release announcement. A version bump in source does not mean packages or binaries have been published.
What shipped in 0.10.0
What 0.10.1 is: finish what we started
Each item below already has one or more partial fixes behind it. 0.10.1 closes those gaps instead of adding scope. CI and release-pipeline fixes land first, because every other change lands through that gate.
Product fixes
crashes/, an on-screen "turn stalled" status, and stream timeouts well under the current 900s default. Engine silently freezes mid-run: user messages are persisted but never answered; no error, no log line, no crash entry #6184 stays open until a real field trace confirms the root cause, so related commits sayRefs #6184.stopends the turn (ACP follow-up: empty terminal responses and Full Access discovery #6310). When a model returns a cleanstopwith no text and no tool call, the turn should retry a bounded number of times and then fail visibly. The same handling must apply on the ACP serve path.git_fetchcan hang on a credential prompt. Tool-side git spawns should never prompt on the terminal (GIT_TERMINAL_PROMPT=0, SSH in batch mode), and fetch should run under a timeout.[↵]cue flickers on each keystroke. The fix is already written; it needs to land with the updated test.base_url(Delete the legacy root base_url and migrate to [providers.<name>] base_url #6394, Model pins don't propagate: fleet members and agent profiles keep a retired id after the provider moves on #6035). Contributor PR fix(api): expose user-defined [providers.<name>] routes to native clients #6404 lands as its own PR. After that, migrate the rootbase_urlinto the matching[providers.<name>]entry and warn, without rewriting, when a pinned model is no longer in the roster.0.10.0./contextshows a different number from the meter. Make/contextlead with the same estimate the meter and the auto-compact gate use./debug cachestatus lines, makeremote-setup --applyeither work or exit non-zero, and correct the glibc/GNU wording (both Linux assets are static musl).CI and release pipeline (these land first)
main, so a green PR cannot turnmainred. Each ratchet gets an update command so the fix lands in the same PR.Also open in this milestone
Not in 0.10.1 (planned for 0.11 or later)
ACP sessions on the full turn runtime (#5835), the session-store rewrite (#6144), sub-agent decomposition (#6293), the catalog single-authority work (#6396), the
context_statustool (#6217), and test-environment convergence.Where work is tracked
How PRs land
Fixes #NorCloses #Nonly when the PR really resolves the issue. Otherwise useRefs #N.How to report
codew --version(with the build SHA), and the client and operating system you used. For a freeze, say what the turn was doing when it stopped, and attach anything that appeared incrashes/.How to help
agent-readyandgood first issue. Before you start, check the latest issue comments and linked PRs.