CCARF Practice Question

Paper 5 · Question 21

D3 Claude Code Configuration & Workflows · Paper 5

[Scenario: Claude Code for Continuous Integration] Your pipeline script runs `claude "Analyze this pull request for security issues"`, but the job hangs indefinitely. Logs show Claude Code is waiting for interactive input. What is the correct approach to run Claude Code in an automated pipeline? What is the correct approach?

• A.Add a `--batch` flag: `claude --batch "Analyze this pull request for security issues"`.
• B.Add the `-p` flag: `claude -p "Analyze this pull request for security issues"`.
• C.Redirect stdin from `/dev/null`: `claude "Analyze this pull request for security issues" < /dev/null`.
• D.Set the environment variable `CLAUDE_HEADLESS=true` before running the command.

Show answer & explanations

Correct answer: B

A: The Claude Code CLI has no --batch flag for this. Non-interactive mode is -p or --print.

B: The `-p` (or `--print`) flag is the documented way to run Claude Code non-interactively. It processes the prompt, prints the result to stdout, and exits without waiting for user input—ideal for CI/CD pipelines.

C: Closing stdin does not put Claude Code into print mode. It is waiting for interactive input by design.

D: CLAUDE_HEADLESS is not a Claude Code setting. The process still waits.

Related Claude Code Configuration & Workflows questions

More: Paper 5 · All practice questions