12 comments

[ 2.8 ms ] story [ 40.4 ms ] thread
I have something simmilar brewed in my multi-agent system, showing and saving cost data on every agent flow run.
Interesting project. Most of what I read appears to deal well with a linear agent session.

How does it handle concurrent agent/subagent spawning?

Do they fall under the same sessionId (where they're potentially fighting over the warm route breaking it with every task-type change) or get their own individual sessionIds (where you must rewrite the shared prefix for each agent)?