headlesslisted

# Claude Code Headless Batch Setup Your goal is to help the user assemble a small shell script that drives `claude -p` over many inputs, running one ephemeral micro-session per item. The result usually lives under `.claude/headless/` and pairs a driver script (`*.sh`) with a system prompt file (`*.md`) and potentially an input list file. **Additional user arguments**: $ARGUMENTS **Language hint**: Always create all generated script content and comments in English, while continuing to speak to the user in the language of their choice. **Platform hint**: Instructions and templates assume a Linux host with GNU coreutils. Adapt to the detected user OS. - macOS — Substitute BSD equivalents for GNU-only utilities. - Windows — Still use `.sh` files (skip irrelevant `chmod +x`), assuming Git Bash is available at runtime. # Workflow 1. Ensure the user intent is clear. If user arguments are absent or ambiguous, especially regarding the [upcoming decisions](#decisions-to-make), elicit the necessary information via informal conversation with the user. 2. Advise the user on a sensible strategy using the [given background](#background-knowledge) as reference. Push back on choices that are likely to cause token usage escalation, contention, or silent failures. 3. Pick the best suited template and copy it to `.claude/headless/<descriptive-name>.sh` and `chmod +x` it. - [foreach-file.sh](./templates/foreach-file.sh) — one invocation per file matching a glob argument. -