Codex (OpenAI)

Tested with GPT-5.6-terra, medium reasoning.

• Works well as the Reviewer. Codex checks the Draftor's plans and code before they are approved.

Start Codex with gator loop codex

1. Open a terminal in the repository root and run:

   gator loop codex

   Gator prepares a separate Codex profile for loops (~/.gator/adapters/codex/loop-home) and starts an interactive Codex session in the repository. The first time, Codex asks you to sign in to this profile.
2. Join the loop. Give Codex the participant prompt for its role from the Loop workspace.
3. Enter the goal prompt below in the same Codex session. Codex then stays in the loop until it ends.

Keep Codex in the loop with /goal

Paste this into the Codex session after it has joined the loop.

/goal Remain an active participant in the Gator loop I just joined until it reaches a terminal state. Follow the Gator loop protocol exactly. Run every `gator loop` command as one plain command with nothing added (no `; exit $LASTEXITCODE`, no second line) and judge the result by Gator's printed text, not the exit code: `Your turn: YES` means act, `Loop ended.` means stop. If it is not my turn, use the existing role token and reissue `gator loop wait --token <token> --max-seconds 3600` each time it prints that it is still waiting. Stay connected through paused and blocked states. When my turn arrives, perform the required governed review or submission through the CLI. Do not edit loop files directly or submit without completing the required work.

Copy did not work here. Select the prompt above and copy it.

• Leave <token> as it is. Codex uses the role token from its join. Do not paste the token into the prompt.
• Why the wait is 3600 seconds. Each wait that ends without a turn costs Codex a model turn. An hour-long interval keeps that cost low: at most one such turn per hour, instead of one every six minutes with the protocol default of 360. The wait returns as soon as it is Codex's turn, so it does not delay the loop.

Opus (Anthropic)

Tested with Claude Opus 5.5.

• Works well as the Draftor. Opus writes clear plans and implementations for the Reviewer to check.
• No extra setup. To join the loop, copy the participant prompt for its role from the Loop workspace and paste it into Claude Code. Opus waits for its turn with a background watcher, so it needs no goal prompt.