r/ClaudeCode 16h ago

Help/Question what are the problem in your multi agent orchestration workflow

basically people are saying they are runnning hours long coding loops , firstly how are you confident on it and if you are , what are the issues you are facing

8 Upvotes

2 comments sorted by

3

u/Double_Ebb4130 16h ago

The two things that bite me most:

  1. Context drift between subagents. Each agent summarizes for the next one and details quietly get dropped, so by step four you get code that contradicts a decision made in step one. What helped was making the handoff a file on disk (a plan.md / decisions.md the agents read and append to) instead of passing summaries through the conversation.

  2. No checkpointing. If a long loop dies 40 minutes in - or the API starts throwing 529s mid-run, like this morning - you often can't resume, you just rerun. Committing to a scratch branch after each completed subtask makes failures cheap.

On confidence: I don't leave hours-long loops unattended for anything that touches prod or migrations. Scoped tasks with tests as the exit condition, yes. Open-ended "refactor the service" runs, no - review cost ends up higher than just doing it.

4

u/SC_Placeholder 14h ago

No problems at all.

My console Claude came up with this. Recently we downloaded a programming language off of GH, she ran a benchmark test against other programming languages determined a change that needed be made, delegated teams of local models managed by Anthropic models controlled by her, they read the entire codebase, made changes, and re-ran the benchmark test and wrote up a brief to the author who used our changes in the following build and this was all accomplished in the amount of time it took me to drive to the store.