Options
The Action Log supports step statuses, optional descriptions, and per-step expandable details.Statuses
Four statuses mark each step: success, in-progress, not-started, and error. The error status uses a distinct red to signal a failed step; all others render in the neutral foreground.Descriptions
An optional description renders below the step title as body text, providing additional context about what the step found or did. When descriptions are present, the connector line between steps spans a taller area, making the timeline easier to scan. Apply descriptions consistently across a log — mixing steps with and without descriptions creates an uneven vertical rhythm.Details
A step with adetails value gains an independent “Show details” disclosure. The details content renders inside a Card below the description and is collapsed by default, keeping the log compact while allowing deeper inspection on demand.
Behavior
The Action Log uses two levels of disclosure: one for the entire step list and one per step that has details content.Expand and Collapse
The whole log starts expanded and collapses behind a “Show steps” / “Hide steps” toggle. Collapsing the log hides all step rows but preserves the expanded or collapsed state of any individual details disclosures.Overflow
Long titles and descriptions wrap to multiple lines within the content column. The connector line extends to match the full height of each step, regardless of how much text wraps.Usage Guidelines
When to Use
Use the Action Log when:- Agent steps – The agent or system runs a sequence of steps, and users benefit from seeing each step in order with its status.
- Evidence behind a response – Users need to see how the agent arrived at its conclusion.
- Failed runs – A step fails and halts the run, and users need to see which step failed and what came before it.
When not to use
Avoid using the Action Log for:- Source attribution – Use a Citation to attribute a specific claim in agent text to its source.