While running tasks on Windows (dev mode), I noticed the activity view, the list of tool calls, the agent performed only exists while the run is streaming. The moment the run completes (or on agent switch / reload), it's gone. The replay path that reconstructs conversations discards
tool_execution_* events, so a finished task shows only the final message, with no record of what the agent actually did.
The launch post's framing "every task leaves a trace you can read" is exactly right as a goal, and most of the pieces seem present already: the live activity rendering during streaming, and the replay event stream on load.
I'd like to take a crack at this: keep the activity block after completion (collapsed, reusing the existing UI), and reconstruct it on conversation load from the same replay path. Happy to adjust the shape if you have a different direction in mind.
While running tasks on Windows (dev mode), I noticed the activity view, the list of tool calls, the agent performed only exists while the run is streaming. The moment the run completes (or on agent switch / reload), it's gone. The replay path that reconstructs conversations discards
tool_execution_*events, so a finished task shows only the final message, with no record of what the agent actually did.The launch post's framing "every task leaves a trace you can read" is exactly right as a goal, and most of the pieces seem present already: the live activity rendering during streaming, and the replay event stream on load.
I'd like to take a crack at this: keep the activity block after completion (collapsed, reusing the existing UI), and reconstruct it on conversation load from the same replay path. Happy to adjust the shape if you have a different direction in mind.