Claude Code Headless Mode

Build and run claude commands for work that should be executed through Claude Code itself.

Reference	Read it when
references/flags-and-permissions.md	The command needs more than `-p` — permission modes, tool scoping, output formats, flag inventory, installation
references/examples.md	You want a worked command for a specific shape of task (read-only analysis, safe edit run, JSON report, resume, MCP, sandboxed unattended run)

Requires the claude CLI installed and authenticated on the target machine.

Core rules

claude --help on the target machine is the compatibility floor. CLI flags and permission-rule syntax move faster than docs and copied examples, and they differ between builds. Verify any uncommon flag there before emitting it.
Do not add --model unless the user asked for an override or the workflow must pin a model for reproducibility. The user's configured model is the right default.
Prefer --append-system-prompt over --system-prompt unless replacing Claude Code's default behavior is the point.
Choose the least-permissive mode that still fits the task. acceptEdits is the usual starting point for coding automation. For a truly unattended run, reach for explicit permission rules or dontAsk first; bypassPermissions is only for an already-isolated environment.