$ the-wire · showcase
Stale exec signatures and a docked Command Center
By RepoJournal · Filed · About OpenAI · Composed from the cited sources · methodology
Codex moved on two fronts today: making the Code Mode tool catalog honest after a global helper changes, and reworking where the TUI puts the things that compete with the transcript.
Refresh the Code Mode exec catalog when helper signatures change (#63046) openai/codex
Incremental updates to nested tools could leave the model holding a stale functions.exec declaration when a global helper's signature shifted, for instance when resuming a session with unified image budgeting changes what image advertises. Codex now tracks the signatures of global helpers supplied by the description renderer and redeclares the full functions.exec catalog whenever they change, i...
Forward TUI clipboard copies to Rex clients openai/codex
A client can attach to a Rex session after Codex starts, and a native clipboard write that succeeds on the host never reaches it. Rex now selects OSC 52 forwarding whenever shared terminal detection identifies the environment, even when native copying works, while tmux, Herdr, and SSH keep their environment-based routing.
Suppress TUI completion popups in shell mode (#63054) openai/codex
Shell syntax like PowerShell's $env:HTTP_PROXY was popping Codex completion menus mid-command. Popups now stay shut in ! shell mode and any active file search is cancelled, with dismissals preserved across entering and leaving that mode.
Dock the Agent Command Center beside the conversation openai/codex
The Agent Command Center used to open as a modal and interrupt the conversation view. With features.tui_workspace enabled in owned transcript mode it now opens to the left of the conversation on wide terminals, focused panes fill the screen on narrow ones, and opening a task returns focus to the transcript.
Skip empty permissions messages in the initial context openai/codex
When resolved permission and approval guidance came back blank, the initial context still carried a developer message wrapping nothing but the permissions shell; that message is now omitted for empty or whitespace-only guidance while a permissions checkpoint stays in place for later turns.