Skip to main content
An agent run is a recorded agent session. It captures the prompt conversation, tool calls, model activity, status, usage, and trace data for one session. Use agent run history when you want to understand how an agent responded, why a tool was called, where a session failed, or what a running session is doing.

​
Where to find agent runs

Open History in the web app, then filter Type to Agent. Select a run to inspect its details. The History page is shared across agent and workflow runs. See Run history for the full table, filters, statuses, and detail tabs.

​
What starts an agent run

Agent sessions can start from several places:
SourceExample
API or CLI promptkeystroke agents prompt support --message "Help me"
GatewayA Slack thread routed to an agent
TriggerA webhook, schedule, or poll attachment that invokes an agent
WorkflowA workflow step that calls Agent.prompt()
Another agentA subagent tool call
Follow-up prompts with the same sessionId continue the same session instead of creating a separate one.

​
Inspect the conversation

For agent runs, the detail panel’s Overview tab shows the recorded conversation. User and assistant messages are shown in order, and assistant messages can include collapsed details for:
DetailWhat it helps with
ThoughtReasoning or thinking output recorded by the model
Tool callTool name, arguments, and result or error
ErrorSession error payload for failed runs
The Metadata tab shows run identity, actor, project, trigger, timing, models used, services used, and cost. The Trace tab shows raw spans and logs when trace data is available.
Conversation history depends on what the runtime recorded for that session. If no messages were recorded, the detail panel shows an empty conversation state.

​
Use the CLI

Use keystroke agents sessions when you know which agent you want to inspect: 
keystroke agents sessions list support --status failed
keystroke agents sessions get support <session-id> --include messages,trace
Use keystroke history when you want cloud history across agents and projects: 
keystroke history list --kind agent
keystroke history get <run-id>
agents sessions follows the resolved CLI target, so it can inspect local sessions while you are developing and cloud sessions after deploy. history is for platform run history in the active organization. See the CLI reference for command details.

​
Next steps

Run history

Learn the shared History table and detail panel.

Run agents

Start and inspect agent sessions.

Build agents

Define agents, tools, models, and runtime behavior.

Workflow runs

Compare agent sessions with workflow executions.