Parallel and unattended
Worktrees, parallel sessions, headless runs, CI and schedules: Claude Code when you are not watching.
6 chapters · 23 min
Start the course- 1One checkout per agentTwo agents editing the same folder overwrite each other. A worktree gives each session its own files and its own branch, so parallel work stays separate until you merge it.4 min
- 2Claude Code without a terminalclaude -p runs the same agent loop once and exits, which makes it a command you can pipe, script and schedule. The flags decide whether it stays predictable.4 min
- 3Claude Code on your pull requestsThe Claude Code action runs the agent inside a GitHub workflow, either waiting for an @claude mention or running a prompt on any event. Setup is short; the access and secret choices are where it goes wrong.4 min
- 4Work that runs on a clockClaude Code has three places to run something repeatedly: cloud routines, Desktop scheduled tasks and the in-session /loop. They differ in where they run, how often they can fire and what survives.3 min
- 5Settings a team can shareClaude Code reads settings from several scopes and merges them by a fixed order. Knowing which file wins, and what belongs in git, is what keeps a team's rules from becoming one person's habits.4 min
- 6Running with nobody watchingWhen no one can answer a prompt, the permission rules are the only supervisor left. The safe setup is narrow allow rules, hard deny rules, a capped run and nothing valuable within reach.4 min