Dev.to AI 🤖 Ai 👁 0 📖 2 min read

Codex CLI 0.171.0 Turns Its Terminal Workspace On by Default — and Lets Scripts Attach to a Running Server

OpenAI shipped Codex CLI 0.171.0 on November 20, 2026, and the headline change is not a model — it is the shape of the terminal itself. The release notes are on GitHub: https://github.com/openai/codex/releases/tag/rust-v

OpenAI shipped Codex CLI 0.171.0 on November 20, 2026, and the headline change is not a model — it is the shape of the terminal itself. The release notes are on GitHub: https://github.com/openai/codex/releases/tag/rust-v0.171.0

What changed

  • GPT-6.2 Sol and Astra join the model catalogs, and Sol is now the default catalog selection.
  • The TUI workspace is on by default. Searchable document previews, image previews, and subagent transcripts now sit beside the main conversation, instead of living behind an opt-in flag.
  • Configurable undo and redo shortcuts arrive in the non-Vim prompt composer, restoring attachments and large pastes along with the text.
  • codex exec --remote <ADDR> starts or resumes noninteractive sessions on an existing app server. /rc and /remote manage local remote control and show device pairing codes from the TUI.
  • Custom MCP status lines can be selected and authored through /statusline when tui_extensions_statusline is enabled.
  • Fixes worth noting: drafts, queued follow-ups, and interrupted input now stay with their original threads when switching or resuming sessions; permission profiles survive working-directory changes; late completion events no longer cancel approvals for a newer turn; and enterprise MCP sign-in is fixed for identity providers that issue ID tokens without refresh tokens.

Why it is worth paying attention to

The workspace going default-on is a statement about what a terminal coding agent is for now: supervision, not just chatting. The relevant context — files, images, what subagents did — stays visible next to the conversation instead of buried in scrollback. That only helps if the extra chrome stays out of the way on small terminals and laggy SSH sessions, which is the first thing to watch in practice.

codex exec --remote is the quieter but more consequential change for automation. Scripted loops and CI jobs can attach to a warm server instead of cold-starting Codex on every run. That turns the CLI from a one-shot tool into something you can keep alive as a service — and it raises the obvious follow-up question about auth and pairing on shared servers, where the release notes are still thin.

Making Sol the default catalog pick says something about where the defaults are being tuned: the efficient model first, the frontier model on request. Worth watching whether that changes output quality on long agentic sessions, and how many people switch back to Astra for the hard tasks.

Open questions

  • How does the default workspace behave on small terminals or over a slow SSH connection?
  • What is the security story for a long-lived app server once --remote is in everyday use?
  • If Sol is the default, how visible is the switch — and does it change results on multi-hour agent sessions?

What are you watching for in this release?

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.