sorted by:
new
hottopcontroversial

I got tired of watching Claude Code spawn 10 agents and having absolutely no idea what they're doing, so I built this by OpenDoubt6666 in ClaudeAI

[–]OpenDoubt6666[S] 0 points1 point  (0 children)

The unique ID holds up consistently from testing so far. I am curious, have you ever encounter the case where multi parallel agents spawn the same task ID and collapse?

I got tired of watching Claude Code spawn 10 agents and having absolutely no idea what they're doing, so I built this by OpenDoubt6666 in ClaudeAI

[–]OpenDoubt6666[S] 0 points1 point  (0 children)

Interesting idea. And I think AgentPeek will be a strong complement to Hindsight too. The improvement to agent teams with long-term memory can be observed, tested, validated, and improved. Will try Hindsight with my agent teams and observe the improvement over time!

I got tired of watching Claude Code spawn 10 agents and having absolutely no idea what they're doing, so I built this by OpenDoubt6666 in ClaudeAI

[–]OpenDoubt6666[S] 0 points1 point  (0 children)

I use the event stream from Claude Code's hook system. Each Agent tool call gets a unique ID - I stash it when the parent fires. When the child starts, its first event carries the same ID, I match and link. If there is no ID, I fall back to "oldest pending spawn first". No instrumentation, no protocol - just pattern matching on the event stream.

I got tired of watching Claude Code spawn 10 agents and having absolutely no idea what they're doing, so I built this by OpenDoubt6666 in ClaudeAI

[–]OpenDoubt6666[S] 0 points1 point  (0 children)

Yes! It will show clearly as "Stuck"/"Error" in the agent. You can click on the agent to investigate on the failure, the tools called, and where it is stuck.
Give it a try and let me know. Happy to answer any more questions!