Playbooks · Coding tasks
Codex 0.171 turns on the TUI workspace
Written November 20, 2026
Codex 0.171 enables the TUI workspace by default, adds codex exec --remote and /rc remote control, and makes GPT-6.2 Sol the default catalog model.
Updating to Codex 0.171 changes the terminal you open by default. The TUI workspace is now on without anyone turning it on, so document previews, image previews, and subagent transcripts sit beside the main conversation from the first session. The same release changes how a script drives an existing app server and how remote control is paired from inside the TUI. None of this needs a migration, but all of it is easier to meet on purpose than by surprise.
The workspace is the default now
The 0.171.0 release notes say the TUI workspace is enabled by default, with searchable document previews, image previews, and subagent transcripts alongside the main conversation. Each part of that sentence does different work. Searchable document previews mean a file the agent is discussing can be read and searched in place instead of opened elsewhere. Image previews put visual material in the same view as the conversation about it. Subagent transcripts alongside the main conversation make delegated work visible while it happens, rather than something to reconstruct afterward from a summary. Together they move the TUI closer to a working surface and further from a single scrolling prompt — and because the workspace is the default, that shift arrives with the update itself, not with an opt-in a user might never find.
Driving an existing app server from a script
The notes add codex exec --remote <ADDR> to start or resume noninteractive sessions on an existing app server. The distinction that matters is the existing server: instead of each scripted run standing up its own isolated session, a noninteractive run can now be aimed at a server that is already running, and a session there can be resumed as well as started. For anyone who automates Codex — a scheduled check, a pipeline step, a repeated task — that changes the shape of the setup. The script no longer has to treat every invocation as a cold start. Scripts written against the older behavior should be reviewed with this option in mind, because starting fresh and resuming are different choices.
Remote control managed from the TUI
Two new commands, /rc and /remote, manage local remote control and display device pairing codes from the TUI, according to the notes. Pairing is the step people usually have to hunt for: which screen shows the code, and where does it get entered? Putting the pairing codes inside the terminal interface answers the first half of that question in the place the user is already working, and managing local remote control from the same commands keeps the whole flow in one spot. If you pair a device with Codex, expect to start from /rc or /remote in this release.
Composer undo, and a customizable status line
The non-Vim prompt composer gains configurable undo and redo shortcuts, including restoration of attachments and large pastes. That last clause is the practical one: losing a large paste or an attachment to a stray edit is a real cost in a long prompt, and undo that restores them — not just the text — makes the composer safer to edit in. Because the shortcuts are configurable, users with established habits can fit them to what their hands already expect instead of learning a fixed new pair.
The release also adds custom MCP status line selection and authoring through /statusline when tui_extensions_statusline is enabled. Note the condition: this one is gated behind that setting, unlike the workspace, which is simply on. Users who want to choose or write their own MCP status line get a command for it; users who never enable the setting will not see a change.
The new default model
GPT-6.2 Sol and Astra are added to the model catalogs in this release, with Sol as the default catalog selection. That is the whole of it here: a user who picks a model from the catalog, or who accepts the default, will meet Sol first. Anyone who has pinned a different model should check what their setup actually selects after updating, since a changed default only matters where the default is what gets used.
The previous release's terminal work — realtime voice in the TUI — is covered in Codex 0.170 adds realtime voice to the TUI. The 0.171 notes do not revisit it; this release's weight sits in the workspace, the remote execution path, and the pairing commands.
Who should update first
- Anyone who scripts Codex.
codex exec --remotegives noninteractive runs a way to start or resume sessions on an existing app server instead of always starting cold. - Users who work with documents, images, or subagents in the TUI. The workspace is now the default view, with previews and subagent transcripts beside the conversation.
- Anyone pairing a device for remote control.
/rcand/remoteare where pairing codes are displayed and local remote control is managed. - Long-prompt writers. Configurable undo and redo in the non-Vim composer restore attachments and large pastes, not just text.
Related playbooks
- Codex 0.170 adds realtime voice to the TUI
- Foundry retires codex-mini on November 15
- ChatGPT and Codex share one token budget
- Cloudflare runs the Codex loop in a Durable Object
Sources
- Codex rust-v0.171.0 release notes — OpenAI Codex on GitHub — GPT-6.2 Sol and Astra in the model catalogs with Sol as the default, the TUI workspace enabled by default, configurable composer undo and redo, codex exec --remote, /rc and /remote, and the custom MCP status line through /statusline.
Back to: Coding tasks playbooks hub · Also: Codex 0.170 adds realtime voice to the TUI