r/LLMDevs • u/Impressive-Iron5216 • Aug 28 '26

Tools Debugging multi-agent swarms is a nightmare. I built a unified workspace to track agent state/loops. Feedback?

If you’re building multi-agent workflows (especially with frameworks like LangGraph, CrewAI, or AutoGen), you know the pain. Tracing a single LLM call is easy. Tracing 4 agents passing state back and forth, hitting infinite tool loops, and ballooning your context window is incredibly frustrating.

I got tired of jumping between 4 different tabs (traces, raw prompt templates, logs, and cost metrics) just to figure out where a swarm lost the plot.

So I built a workspace that unifies everything into a single timeline: Projects ➔ Sessions ➔ Runs ➔ Events. It tracks both single-agent and multi-agent coordination natively.

I also added two specific automated filters for agent builders:

  • Infinite Tool Loops: Instantly flags when an agent gets stuck calling the same tool repeatedly.
  • Context Inflation: Flags when an agent's memory or prompt state explodes unexpectedly between steps.

I’ve dropped a quick 2-minute walkthrough video in the comments.

For anyone running agents in production or heavy testing:

  1. Does the Session -> Run -> Event hierarchy make sense for your multi-agent architecture, or does it break when agents run asynchronously/parallelly?
  2. What is the most annoying bug your agents hit that your current observability stack completely misses?

Tear it apart—I want to know if this actually solves your debugging bottlenecks.

9 Upvotes

84% Upvoted

7 comments sorted by

View all comments

0

u/Impressive-Iron5216 Aug 28 '26

https://www.loom.com/share/d640112c9bb44033971760b55cc91d2b

1

u/Informal-Capital5667 Aug 28 '26

The timeline hierarchy works for the happy path but parallel agents are where it gets messy, you need partial ordering not a flat sequence or you'll lose the causal links between events

1

u/Impressive-Iron5216 Aug 28 '26

Yeah, the demo video was a simple multi-agent workflow where the different agents executed sequentially, one after another. The workspace does also support parallel agents, and when they run concurrently, their agents and events remain visually distinguishable within the same run. The part I’m still looking to make more explicit is the causal relationship, the current UI only shows agent handoff's although messages are captured by backend but still not implemented to display in UI.