Give each parallel agent its own checkout and a claimed task

Each agent works in its own container or worktree and claims a task with a lock file before it starts.

Prompt

Evaluate and apply this CI technique to my repository: Give each parallel agent its own checkout and a claimed task.

Each agent works in its own container or worktree and claims a task with a lock file before it starts.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/isolated-agent-checkouts.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Anthropic used this technique

Read what Anthropic changed and follow the original sources.

Give each parallel agent its own checkout and a claimed task

In Anthropic's C compiler project, each agent runs in its own Docker container, clones the shared repository to its own workspace and pushes from there. An agent takes a lock on a task by writing a text file to current_tasks/, so git's synchronization forces a second agent that claims the same task to pick a different one. Bun's Rust port split its work into 4 workflow shards, each in its own worktree and running 16 Claudes, and told the agents to avoid git stash, git reset and any git command beyond committing specific files.

Use it when: Several agents push to one repository, or two agents pick up the same task.
Before applying it: Task locks are plain files in the repository, so merge conflicts are frequent and the agents resolve them. Keep slow shared commands out of the agents' loop.

How Anthropic used this technique

Give each parallel agent its own checkout and a claimed task

Company Playbooks