Events
The Events view groups recorded sessions by agent and displays the selected session as a chronological event chain.
Session List
Section titled “Session List”Each session row can show:
- Session ID.
- Start date.
- Turn count.
- Event count.
- Provider-reported cost.
Use the search field to find a session and the copy action to copy its ID. Long lists load additional sessions as you scroll.
Event Filters
Section titled “Event Filters”Filter chips can narrow the chain to event methods such as requests, responses, tool calls, usage, debug events, and memory actions.
Available event types depend on the runtime version, agent configuration, and what happened in the session. For example, debug events require Debug mode.
Reading The Chain
Section titled “Reading The Chain”The timeline gives specialized views for common events:
- User requests and agent responses.
- Clarification questions.
- Recorded tool IDs, parameters, and returned data.
- Memory reads and writes.
- Token and cost usage.
- Debug request and response details.
Unknown or newer methods are still displayed with their raw content.
Start with the first unexpected event and follow the chain forward. For tool failures, confirm the requested tool ID and parameters, then inspect the skill flow, Catch nodes, and application logs for its outcome.
The current grouped execution path does not guarantee a separate stored
tool.response event for every successful result. A missing Tool Response card
therefore does not by itself prove that the skill failed. Use the following
agent request or response, flow-level logging, and the skill’s own error path to
confirm what happened.
Session Usage
Section titled “Session Usage”The footer shows total recorded tokens and USD cost for the selected session. Cost depends on the provider reporting it.
Export
Section titled “Export”Export downloads the complete session event log in:
- Plain text (
.txt) - Markdown (
.md) - JSON (
.json)
Exports include the session ID, export time, and all loaded event content in chronological order.
Sensitive Data
Section titled “Sensitive Data”Event logs and exports may contain prompts, memory, system instructions, model output, tool parameters, tool results, user data, and debug information. Review and redact them before sharing.