parallel-autonomous-agentslisted

# Parallel autonomous agents Source: [Building a C compiler with a team of parallel Claudes](https://www.anthropic.com/engineering/building-c-compiler). The lock-file mechanism exists as a standalone framework (`claude_code_agent_farm`); the autonomy loop exists as other skills. No skill packages the two together for a shared git repo, and most skills coordinate by git worktree instead, which this contrasts against. The goal is sustained parallel progress on one codebase with nobody watching. Several agents run at once, each claiming work, doing it, and moving to the next thing on its own. Two mechanisms make that safe: a loop that keeps each agent going, and a lock protocol that keeps them off each other's toes. ## The autonomy loop Each agent runs in a loop that picks the next task, does it, and respawns without pausing for a human. A simple shape is a script that calls a headless agent CLI (`claude -p`, `opencode run`, or any other) in a fresh container per session, so context never accumulates across tasks and a wedged session cannot poison the next. The loop is what turns a one-shot agent into one that works through a backlog overnight. ## Lock files claim work Coordinate through the repo itself. To take a task, an agent writes a lock file naming it, then works on an isolated clone: 1. Claim by writing `current_tasks/<task>.txt`. 2. Work on a private clone of the repo. 3. Pull and merge upstream before pushing, so concurrent work integrates. 4. Push the result. 5.