Describe the enhancement you want to request
When tools execute (file reads, grep, edits, bash commands, etc.), there's no indication of when they started or how long they took. This makes it hard to identify slow tools or understand the timeline of an agent session.
Proposed change: Display a clock timestamp and running duration on each tool execution block — both in the web UI and TUI. For example: 02:03 PM · 5s while running, updating live. Interrupted/aborted tools should show a distinct "Interrupted" indicator instead of a misleading duration.
Benefits:
- Quickly identify which tools are slow
- Understand the timeline of a session at a glance
- Clear visual distinction between completed, running, and interrupted tools
Describe the enhancement you want to request
When tools execute (file reads, grep, edits, bash commands, etc.), there's no indication of when they started or how long they took. This makes it hard to identify slow tools or understand the timeline of an agent session.
Proposed change: Display a clock timestamp and running duration on each tool execution block — both in the web UI and TUI. For example:
02:03 PM · 5swhile running, updating live. Interrupted/aborted tools should show a distinct "Interrupted" indicator instead of a misleading duration.Benefits: