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

How to build with Opus through Claude Code, then check in Codex with Codex on Crack

Let Opus implement a whole assignment, then have the Codex host verify it in the browser.

Credentials. The Claude Code CLI uses your own subscription login, so you are responsible for keeping that authentication secure.

Who it is forA developer who prefers Claude for a build but wants Codex tools, such as browser checks or computer tools, to verify the result.

The problemExternal Claude sessions do not inherit Codex tools, so checking the finished build usually means a manual handoff.

The outcomeOpus implements the assignment through Claude Code, and the Codex host runs the requested browser or computer checks and reports the evidence back.

What you need first

  • Node.js 24.15 or newer
  • A Codex client with plugin support
  • Model access you already have, and a compatible configured route for native workers
  • The official Claude Code CLI, authenticated through your subscription, for Claude mode

Steps

  1. Install the Claude Code CLI and confirm it is authenticated through your subscription.
  2. Run codex plugin marketplace add "$PWD" from this checkout in a stable folder.
  3. Run codex plugin add codex-on-crack@codex-on-crack.
  4. Start a fresh conversation and ask Codex to have Opus implement the assignment through Claude Code.
  5. Ask the Codex host to check the result in the browser and report what it found.

Prompt for your agent

With the codex-on-crack package in <project folder>, have Opus 5.5 implement <assignment> through Claude Code, then ask the Codex host to open the result in the browser and report any problems. Expected output: the implementation plus a browser check summary. Verify that the browser evidence comes from the Codex host, not from the Claude session.

Caveat. The current Claude adapter targets claude-opus-5-5, and other Claude models are not automatically supported.

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