Codex CLI Terminal Workspace Gets Multiple Side-Chat Tabs and Restores Saved Side Chats

CodexView original changelog

Codex CLI 0.169.0 lets the opt-in terminal workspace hold multiple side-chat tabs. Developers can switch between tabs with the keyboard or mouse. Saved local side chats can be reopened after Codex restarts, so side threads no longer disappear with the session.

Key Takeaways

  • Multiple side-chat tabs now live in the opt-in terminal workspace, replacing the single side pane.
  • Tabs switch by keyboard or mouse, so the feature suits both terminal styles.
  • Saved local side chats can be reopened after a restart, so side threads no longer vanish with the session.
  • Side threads keep exploratory questions out of the main chat, which protects the primary context.
  • The terminal workspace stays opt-in, so existing setups are unaffected.
  • The release extends the side conversation pane from 0.168.0 into a more durable multi-thread workflow.

Multiple side chats in one workspace

Codex CLI 0.169.0 builds on the opt-in terminal workspace, which first showed a side conversation next to the main chat. The workspace now supports multiple side-chat tabs, so a developer can keep several parallel threads open beside the main conversation. One tab can hold a quick question about an API, another a scratch investigation, and another a review of a different file, without any of them crowding the primary chat.

Keyboard and mouse switching

Moving between tabs works from the keyboard or with the mouse. Terminal users who prefer to keep their hands on the keys can cycle through side chats. Those who use a mouse-capable terminal can click the tab they want.

Side chats survive a restart

Local side chats are saved, and Codex can reopen them after a restart. Before this release a side thread was tied to a single session, so closing the terminal meant losing that context. With saved side chats, a side investigation can be picked up the next day, which suits long-running work.

Why it matters

Side chats keep exploratory questions out of the main thread's context. Tabs and persistence turn that from a one-off pane into a lightweight set of working notebooks inside the terminal. The workspace remains opt-in, so developers who have not enabled it see no change.