DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to set cross-backend subagent delegation in Codex with Codex ChatGPT Web

Choose between Compatibility V1 and Native subagent delegation for Codex tasks.

Who it is forA developer who runs Codex subagents across different model backends and needs the delegation mode to match their setup.

The problemSubagents across backends may fail or behave differently depending on the protocol, and it is unclear which mode a Codex task uses.

The outcomeYou know the current subagent protocol, and the task runs on the mode you chose after a Codex restart and a new task.

What you need first

  • A ChatGPT account. Model availability depends on your account and workspace.
  • Codex installed and able to show a model picker.
  • A supported system: macOS 13+ (arm64/x64), Windows x64, or Linux x64.
  • For full harness mode: ability to enable ChatGPT Developer Mode and create a Tunnel connector and a regular API key.
  • Bun 1.4.0 only if you run from source instead of the installer.

Steps

  1. Run codex-chatgpt-web subagents status to see the current protocol.
  2. Run codex-chatgpt-web subagents compatibility-v1 to use Compatibility V1, which new installs use by default.
  3. Or run codex-chatgpt-web subagents native to keep Codex's own feature settings and enable plaintext Web-to-Web V2 delegation.
  4. Restart Codex and start a new task after changing the protocol.

Prompt for your agent

Using the codex-chatgpt-web repo, run the subagents status command and report the current protocol. Then set the protocol to <compatibility-v1 or native> and confirm the new value by running status again. Expected output is the two status results and a note to restart Codex.

Caveat. Native mode enables plaintext Web-to-Web V2 delegation, so confirm your data handling is acceptable before switching.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page