Codex CLI adds voice. The recovery fixes matter more

Codex CLI 0.155.0 added experimental voice conversations on 17 September 2026, but the changes I would prioritize are the ones that preserve work: keeping a prompt when context compaction fails and restoring saved tasks after a managed daemon restart. The next day’s 0.155.1 hotfix also matters if your provider rejects reasoning summaries. These are documented client changes, not a new model release. [1]

What does voice in Codex CLI actually do?

The new voice mode lets you have a live conversation inside the terminal interface, with a transcript and audio controls. The implementation includes /voice, /voice mute and /voice stop. It can speak final answers from work delegated during the conversation, while keeping the delegated commentary unspoken. Typed answers are not automatically read aloud. [2]

A feature roundup in r/CodexAutomation on 18 September led with voice, which is an understandable choice: it is the most visible addition. That post is a useful pointer to the release, rather than an independent test of how well voice works. [7]

I would try it for explaining a problem or discussing a proposed change while looking at code. For exact paths and acceptance criteria, I would still want a written instruction I can inspect. The release notes call voice experimental and limit it to supported builds; they do not promise that every installation will expose it. [1]

This changes how you talk to the agent. It is separate from the capability and cost questions in my GPT-6 Astra comparison.

What happens when a long task is interrupted?

Two fixes address different ways a session can lose continuity. The first concerns compaction, the step that reduces conversation context before work continues. Previously, a failure before the next turn could leave an already accepted prompt out of the saved history. The fix records the incoming input before reporting that failure. [4]

That distinction is useful when diagnosing a failed session. An error can still stop the turn, but the instruction should remain available in its history. The regression test described in the change checks that the prompt is saved once and that no additional model request follows the failure. It does not claim that compaction can no longer fail. [4]

The second fix restores saved tasks when the managed daemon, the background service, restarts. Recovery happens in the background, and active goals can continue before a client reconnects. If one task fails to recover, recovery continues for the others. [5]

I read these as improvements to session continuity. They complement keeping useful repository context, which is a separate problem: preserving an instruction does not decide whether the model has the right project facts. The daemon changes also concern the local Codex service, not the hosted Agents API.

Worktree cleanup now tells you whose files they are

The worktree browser now connects a managed checkout with its owning task. It shows the task title, when it was updated, and whether it is archived or unavailable. A worktree is a separate checkout of the repository, so that relationship helps explain why a directory exists before you remove it. [3]

Deletion requires confirmation, defaults to Cancel and preserves conversation history. The implementation restricts removal to managed worktrees in the current repository. It refuses the current checkout and any checkout containing local changes, untracked files or ignored files. [3]

The inclusion of ignored files is worth understanding. A directory can contain generated output that Git normally leaves out of its changes list, and this deletion check still considers it. I would prefer that conservative behavior when cleaning up after parallel tasks. It gives the operator more information before removing files, which matters independently of which agent handles a large feature best.

Why did 0.155.1 change reasoning summaries?

Version 0.155.0 made new local terminal sessions request detailed reasoning summaries by default. Some providers do not support them and rejected the request. The 18 September hotfix restores none as the default while respecting explicitly configured auto, concise and detailed settings. [6]

That is a compatibility fix, not an announcement that the model reasons less. The change concerns the requested summary of reasoning. If you read the 0.155.0 announcement and expect live summaries to appear automatically after updating, the hotfix explains the difference. [6]

The first reports also deserve proportion. One r/codex user reported that 0.155.0 could not initialize the Windows sandbox and that returning to 0.154.0 resolved their problem. That is one user’s report, not a confirmed failure across Windows installations. [8] The documented 0.155.1 fix concerns reasoning summaries, so I would not assume it resolves that separate complaint.

For an existing terminal workflow, I would check prompt preservation and task recovery before spending much time on voice. A new way to give an instruction is useful; being able to find that instruction after an interruption is what lets the work continue.