Skip to content

1.0.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Aug 16:46
v1.0.2
d3049cb

Codex Web GPT 1.0.2

Codex Web GPT launcher

Codex Web GPT launcher

ChatGPT Pro can now be spawned as a native Codex subagent.

Pro as a native consultant

A normal tool-capable agent can collect evidence from the computer and then ask Pro for a long, deep second opinion. With fork_turns="all", the Pro child receives the parent task's retained context snapshot, works inside the original Codex Harness, and returns its conclusion to the parent agent.

This is especially useful because ChatGPT Pro cannot initiate local computer tools itself. Pro remains read-only for the local machine; the change only removes the hardcoded catalog restriction that previously kept it out of Codex's native subagent registry.

Unlike projects that expose ChatGPT as an MCP query tool, this does not ask a separate browser tab for an isolated answer. Pro is the actual model of a native Codex child agent, so Codex owns the fork, context handoff, lifecycle, trace, and result collection. No second ChatGPT-query bridge is needed beyond the normal Codex Web GPT setup.

Stability and recovery

  • Improved launcher and runtime stability on Windows and macOS.
  • Added a persistent bridge switch in Launcher Settings.
  • Disconnecting restores the previous native Codex backend and disables the ChatGPT Web route.
  • Reconnecting starts the bridge again and makes the Web models available. A disconnected bridge stays disconnected after a launcher restart until you reconnect it.

The native-provider passthrough follows the same basic routing principle as OpenCodex: native Codex models still reach the native backend unchanged, and the original model catalog is preserved. The recovery switch therefore does not require sacrificing normal Codex behavior.

Tested

The launcher is manually tested on Windows 11 and macOS. The release pipeline also builds, verifies, packages, and smoke-launches Linux, although I still do not own a Linux machine, so real Linux reports are especially welcome.

What comes next

Stability remains the first priority. Please open an issue if anything behaves incorrectly — I am taking this project seriously and will keep maintaining it.

Next I will keep improving the Pro workflow and explore native support for more providers. Contributions, issues, and forks are welcome. If this project helps you, I would really appreciate a star.

Assets 21
Loading