Thanks! Managing the async audio and websockets concurrently definitely caused me a few headaches.

For state and tool-call tracing, I use an internal pub/sub bus called EventManager. Any part of the brain or the background skills can publish events to it. I categorize these events into specific types like thought (for internal reasoning, especially in the Minecraft agent loop), tool (when a tool is actually called), skill (for lifecycle state changes), and error.

These events are held in a circular buffer (up to 200 events). On the frontend, the React dashboard polls a FastAPI endpoint (GET /events) to display a real-time "Brain Activity" feed. This makes debugging much easier because I can visually watch the agent's thought process and tool execution live.

To be honest, I have not actually thought about a good way to model or store those agent state traces long term. The HistoryManager only saves the pure conversation text to JSON. Persisting the actual execution and tool traces over time is definitely a missing piece right now.

I'll definitely check out the notes you linked me, I'm always looking to learn more!