Claude Print

Claude Print

Run a non-interactive Claude Code CLI print-mode call from Codex. This is the Codex edition's low-level Claude bridge for one-shot review and consultation prompts.

Step 1: Choose Permission Scope

Default to read-only review:

claude -p --permission-mode dontAsk --allowedTools="Read,Grep,Glob,Bash(git diff:*),Bash(git log:*),Bash(git show:*),Bash(git status:*),Bash(git rev-parse:*),Bash(git ls-files:*)" "<prompt>" < /dev/null

The Bash allow-list is restricted to read-only git subcommands so peer review cannot mutate the working tree, branches, or remotes. Use broader permissions only when the user explicitly asks Claude to perform write-capable work.

Step 2: Shape the Prompt

Keep the prompt compact and explicit:

• State that Claude is an independent reviewer.
• Include the exact scope: diff command, files, or plan/spec path. Pass text you did not author through the context file.
• Include the required output contract.
• Tell Claude to verify codebase claims by reading files before reporting findings.
• Tell Claude not to modify files unless the current task explicitly requests write-capable work.

For large context, print the absolute path of the context file first:

mkdir -p "$PWD/.turbo/claude" && echo "$PWD/.turbo/claude/<tag>-ctx.txt"

Write the context file to the printed path with apply_patch so nothing is interpreted on the way in, then substitute that same printed value for <printed-path> below. An earlier cd in a compound command leaves the session in a different directory, so a relative path resolves against that directory instead:

cat "<printed-path>" | claude -p --permission-mode dontAsk --allowedTools="Read,Grep,Glob,Bash(git diff:*),Bash(git log:*),Bash(git show:*),Bash(git status:*),Bash(git rev-parse:*),Bash(git ls-files:*)" "<prompt>"

A cat that fails does not stop the run: Claude executes on the bare prompt, burns the full wait, and returns nothing. Read the stderr for the cat error rather than waiting on the output.

Route text you did not author through this channel whatever its size — a diff, file contents, a code comment, a plan or spec, third-party feedback, command output. Keep backticks and $ out of the quoted argument even in text you wrote, since both stay live inside it.