I’ve been experimenting more seriously with Claude Code and one thing I keep coming back to is what “multi-agent” workflows are actually useful in practice. I don’t mean “I opened 3 terminal tabs and asked Claude to do 3 unrelated things.” I mean something closer to:
- one agent researching / reading the repo
- one agent implementing a change
- one agent writing tests
- one agent reviewing the diff
- one agent checking docs / edge cases / migration impact
- multiple agents working on separate parts of the same feature, then reconciling the work For people who are doing this successfully: What tooling are you using?
- Claude Code directly?
- git worktrees?
- tmux?
- custom scripts?
- Cursor / Aider / Codex / Goose / Devin / something else?
- some kind of orchestrator? How are you preventing chaos?
- merge conflicts
- duplicated work
- agents making incompatible architectural decisions
- tests passing in one branch but not after reconciliation
- one agent “fixing” what another agent intentionally did What is the actual workflow?
- Do you give each agent a written spec?
- Do they share a scratchpad / plan / task file?
- Do you have a lead agent coordinate?
- Do you manually merge the outputs?
- Do you keep each agent in its own worktree? What kinds of tasks does this work well for?
- repo research?
- refactors?
- tests?
- migrations?
- docs?
- bug hunts?
- large feature implementation? I’m especially interested in workflows that people are using repeatedly, not just demos. submitted by /u/1kexperimentdotcom
Originally posted by u/1kexperimentdotcom on r/ClaudeCode
You must log in or # to comment.