Map the new boundary
Record the CLI version, installation source, workspace path, account or organization policy and whether the task uses local previews, an existing app server, remote control or a custom MCP status line. Keep document content, images, tokens and client identifiers out of the handoff unless approved.
Run a bounded staging rehearsal
Use a disposable repository and non-production app server. Test a document preview, image preview, subagent transcript search, remote session start or resume and one undo or redo action. Record the CLI version, workspace, session identifier, server owner and allowed directories.
Keep MCP and model controls separate
The custom MCP status line is a display and selection workflow, while remote sessions determine where a noninteractive task runs. Validate the connected server, permitted tools and model catalog independently. A visible status line is not evidence that a tool call reached the intended environment.
Handoff artifact and limits
The agency handoff should contain the CLI version, workspace and server owner, non-sensitive session identifier, allowed directory boundary, preview and remote-session acceptance results and the rollback or manual-review decision. This article does not claim that a reader's session or repository is affected.
Primary source: ChatGPT and Codex changelog. Technical and editorial review remain pending.