Agent graphs fix handoffs, but every node still rediscovers the codebase
Few_Doughnut4293 · reddit · 2026-07-23
The author split a single agent loop into a planning/implementation/review graph and found that orchestration alone does not create shared understanding.
- The graph improved handoffs and made it easier to budget and debug each step.
- But every node still re-derives the same codebase from scratch, often reaching different conclusions.
- Passing state along edges helps, but it can become stale when the code changes, creating a synchronized wrong answer.
- The post asks what practitioners are actually doing: explicit state, repeated rediscovery, or something better.
- It ends with the core question of what invalidates state when the underlying code moves.
More from coding & agent
- Code review must become an agent-to-agent pipeline, not a human-only loop — bibryam · 2026-07-23
- A meme contrasts happy vibe coding with miserable vibe debugging — miniapeur · 2026-07-23
- Cursor private workers can run on SSH VMs, screenshot shows — davidcrawshaw · 2026-07-23
- An agent hit GitHub Actions limits, spun up a VM, and kept the build running — davidcrawshaw · 2026-07-23
- Async agents fail when users think a 90-second job has frozen — Specific-Point-4026 · 2026-07-23
- Open-source skill scans your codebase first, then writes a README — Shruti_0810 · 2026-07-23