How I run 4 coding agents at once without reading a single transcript

Описание и применение

Автор описывает, как управлять четырьмя AI‑кодировщиками одновременно, используя отдельные git‑worktree, централизованные запросы к пользователю и структурированные отчёты, чтобы избежать конфликтов и сократить время обзора.

Задача

Managing multiple AI coding agents simultaneously leads to overlapping edits, missed prompts, and excessive transcript scrolling.

Результат

The workflow reduces lost edits, centralizes agent prompts, shortens review time to ~20 seconds per task, and enables one-click shipping of changes.

Рабочий процесс

• Create a dedicated worktree and branch for each task using git worktree add -b <branch> <path> origin/main
• Run the agent with a prompt, e.g., claude "fix the flaky auth test"
• Allow the agent to ask questions via the ask_user tool; collect all questions in a single list
• Configure the agent to output a structured report: hero line, diff, test results, callout, next steps
• Review the report; if correct, ship by committing, pushing, and opening a PR with one click; if CI fails, reopen the same session with claude --resume or codex resume
• Use the wisp tool to automate these steps and manage multiple agents concurrently

Доказательства

Two agents in one checkout will eventually overwrite each other. Not with an error: session A fixes a file, session B (working from what it read 20 minutes ago) rewrites the same file, and A's fix is quietly gone.

Источник

Give the agent an explicit way to ask (an MCP tool like ask_user works with Claude Code, Codex and opencode), and route every question into one list.

Источник

So I ask the agent to end with a small structured report (a hero line, a diff, a test result, a callout, next steps) instead of prose.

Источник

If the report looks right, the next step is always the same: commit, push, open a PR, watch CI.

Источник