Codex Web GPT v5.0.1

V5 adds Zero Risk Mode: the full Codex MCP harness still runs through ChatGPT, but the launcher never reads or changes the ChatGPT page and never sends a prompt for you.

V5 highlights

• Zero Risk Mode. The launcher prepares and copies the complete Codex prompt; you paste it into ChatGPT, add any images yourself, select the Codex Zero Risk connector plus the model and effort you want, send it, and confirm Sent. Codex tools, patches, terminal calls, structured output, streaming, and native progress stay available through the same turn-bound harness without browser automation.
• A separate Zero Risk MCP setup. Automatic and Zero Risk modes have independent connector identities, Tunnel IDs, API keys, runtime state, and recovery. Switching modes is transactional and never silently reuses the other mode's private credentials.
• Optional Zero Risk Pro profile. The install menu can add a second ChatGPT Web — Zero Risk Pro row with roughly 250,000 usable tokens before compaction. It is intentionally explicit: select ChatGPT Pro manually for every turn; a Pro account is required, and the larger limit may not work with every effort.
• Manual turns that remain real Codex turns. A neutral request ID binds each ChatGPT response to the exact Codex turn through MCP metadata. Concurrent turns stay isolated; reconnects rejoin the same request; cancellation, completion, retained-chat continuation, and compaction are explicit and fail closed.
• Zero Risk compaction. The active ChatGPT agent produces the checkpoint through the bound MCP control, the old chat is retired, and the compacted Codex continuation starts from a fresh manual chat without exposing private control values in the pasted prompt.
• A clearer launcher flow. First-run onboarding now offers With Automation and Zero Risk, defaults to automation, and keeps the same choice in Settings. The MCP guide includes trimmed, accelerated video walkthroughs with an in-launcher fullscreen viewer.
• Three-language product parity. The new setup, mode selection, manual-turn guidance, diagnostics, and model-profile controls are complete in English, Chinese, and Japanese.

v5.0.1 hotfixes

• Interrupt now retires the exact complete turn. Stopping a Codex turn cancels its matching HTTP stream, browser execution, MCP capability, and structured compaction owner. An interrupt that arrives before ownership registration is also remembered, and a replacement waits for physical teardown instead of inheriting a ghost turn. This fixes the stuck-next-message lifecycle reported in #307.
• Zero Risk outcomes remain truthful. A launcher or runtime failure is no longer relabeled as a user cancellation merely because its own cleanup retires the turn capability.
• Zero Risk → Automatic switches no longer require a launcher restart. The already-loaded browser surface receives its ownership marker inside the same setup transaction, while a failed switch restores the exact previous runtime and mode. Fixes #306.
• Model-switched subagents recover only trusted Codex environment. If Codex omits the complete environment block, the bridge can recover the exact current child rollout from Codex-owned state and canonical JSONL. It validates lineage, turn identity, workspace paths, and sandbox permissions and never treats user-authored XML as filesystem authority. Addresses the remaining case in #288 and the same v5.0.0 spawn failure reported in #314.
• Unrelated Codex configuration is no longer mistaken for bridge drift. Reconnect checks compare only the exact keys managed by Codex Web GPT, preserving unrelated [agents] and [features] settings. Fixes #311.
• Bigger Context uses its real 3× ceiling once. Multipart staging no longer multiplies an already-expanded context limit again, and a Pro rate-limit dialog that appears immediately after submission is now returned as a structured limit error.
• Retired MCP work cannot leak into the next turn. Capability retirement rejects stale tool boundaries, clears obsolete completion vetoes, and settles the previous browser owner before a replacement begins.
• Failed connector verification now leaves actionable evidence. Verify runtime writes an ordered local checkpoint trace of the Temporary Chat surface, composer state, menus, and connector rows while keeping composer text out of the trace. The launcher also records the exact verification failure in Activity, so intermittent reports such as #293 can be diagnosed instead of guessed at.
• Connector setup troubleshooting is explicit. The guide now covers account-matched Tunnel IDs and API keys, tunnel readiness, and the one-time connector retry that ChatGPT may require after its first handshake.

Addresses #288, #306, #307, #311, and #314.

Install

macOS or Linux:

curl -fsSL https://github.com/miuuyy/codex-chatgpt-web/releases/latest/download/install-launcher.sh | sh

Windows PowerShell:

irm https://github.com/miuuyy/codex-chatgpt-web/releases/latest/download/install-launcher.ps1 | iex