u/Federal_Can5247

I'm leading AgentPrism, an open-source tool for visualizing AI agent traces, but I'm not here to pitch it — I want feedback from people building complex agent-style workflows, and this felt like the right room to ask.

I've been experimenting with workflows on different platforms like n8n and Mastra, plus the Claude and Codex CLIs directly. The idea I'm chasing: import AI traces and render the run as a tree, so it's easier to inspect what happened across nodes, retries, branches, and tool calls — instead of scrolling raw spans.

What I'd love to hear from people running this for real:

- What parts of execution debugging are most painful for you?
- Do tree-style views actually help, or do you prefer another way to inspect runs?
- When workflows get large, what information is missing from the standard execution view?

I'll share back what I learn in the comments. Happy to show what we've built if anyone's curious.

I’ve been experimenting with a small workflow around n8n execution logs and would love feedback from people building more complex agent-style workflows.

The idea is to import n8n execution logs and visualize the run as a tree, so it’s easier to inspect what happened across nodes, retries, branches, and tool calls.

For the visualization layer, I’m using AgentPrism: https://github.com/evilmartians/agent-prism

I’m especially interested in learning:

• What parts of n8n execution debugging are most painful for you?
• Do tree-style views help, or do you prefer another way to inspect runs?
• What information is missing from the standard execution view when workflows get large?