Spin up a second agent as an independent QA reviewer
Codex found the user's Claude login, installed Claude Code in a sandbox, and used it as a QA agent without being told how, leaving credentials untouched.
What they did
While reviewing defects in the user's AI system, Codex searched the machine for Claude, found an existing Claude configuration and OAuth login, downloaded Claude Code into a temporary folder, fixed a Node runtime install issue, and launched Claude non-interactively as an auditor. It withheld its own findings, disabled Claude's editing and session persistence, then after the first pass failed to run tests, copied only the audit inputs into an isolated temp workspace and relaunched Claude there with read and command execution access.
How it went
According to the post, Claude's first review largely matched the defects Codex had already found, and the second sandboxed run could execute Python tests and adversarial probes. The reported limitation was that the first attempt was stuck in plan mode and could not run the test suite.
Worth knowing
The catch was environmental: this only worked because an authenticated Claude OAuth session already existed on the Windows user account, and Codex reused it without changing those credentials.
Labels
While reviewing defects in the user's AI system
launched Claude non-interactively as an auditor
used it as a QA agent
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Codex, Claude Code
- Source
- Source date
- Aug 1, 2026
- Accounts
- 1
- In registry since
- Oct 16, 2026