What the source did
- One commenter runs several headless instances in tmux and chains tasks with a bash script.
- Another suggests layering: CLAUDE.md rules, then a few skills, then a typecheck hook.
- Another lays out a safe automation shape that ends in human approval before merge.
Summary written by Agent Cookbook. See the original for the full context.
Copy the prompt
Ours Our version, based on what r/ClaudeCode described. Not their wording. Fill in the [BRACKETS].
claude -p with this prompt, from a script:
Task: [TASK RECORD: repo, path, objective, constraints].
Work only in [PATH]. When done, write handoff.md: files changed, assumptions, tests run, open questions. Do not commit.
(The script then runs [CHECKS] outside the agent and only notifies me if they pass.)
Approval rule
🛡
Plans and merges are approved by a human; the script never auto-merges.
Set it up
- Write a task file per job.
- Run claude -p with --allowedTools limited to what the task needs.
- Run checks outside the agent.
- Review handoff.md and approve the merge.
Common failures
⚠
- Automating plan approval too early.
- No artifact means you can't tell the run happened; always write handoff.md.
Variations
- Same pattern with codex exec.
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy