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

How to let ChatGPT use files and terminal in a Codex task with Codex ChatGPT Web

Connect ChatGPT to a Codex task's files, terminal, and tools through MCP.

Credentials. The setup creates a regular API key and a Tunnel, so store the key securely and revoke it if the machine is shared.

Reverse engineering. Write and modify actions also depend on your ChatGPT workspace and its administrator policy, and the browser integration is unofficial.

Who it is forA developer who wants ChatGPT models to read files, run terminal commands, and use tools inside a live Codex coding task.

The problemBrowser-only ChatGPT cannot see your local project, so you copy code and output back and forth by hand.

The outcomeChatGPT tool calls reach the current Codex task through an outbound tunnel, and the Codex Native2 connector reports as available in Verify runtime.

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. Finish the required setup in the launcher, then open MCP.
  2. Create the Tunnel and a regular API key, then press Connect harness.
  3. In ChatGPT, enable Developer Mode and create a new Tunnel connector named exactly Codex Native2 with Authentication: None and Allow all actions.
  4. In the launcher, run Verify runtime to confirm that Codex Native2 is attached and available.

Prompt for your agent

Using the codex-chatgpt-web repo, guide the setup of Full harness mode for the Codex task in <project folder>. Confirm the connector name is exactly Codex Native2 and that Verify runtime reports it as attached and available. Do not enable auto-approve; report any approval prompts you see.

Caveat. Unexpected approval prompts fail closed unless --auto-approve-tool-calls is explicitly enabled, and that option only clicks Allow once, never a permanent grant.

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