Agent run history
The retrospective log that makes an autonomous run auditable after the fact.
AI & Agents · 7 checks · 12 resources
Before you ship
7- 01Run list with trigger, start time, duration, outcome and cost
- 02Per-run step trace — each tool call with its inputs, outputs and errors, expandable without leaving the page
- 03Artefacts produced linked from the run — files written, records changed, messages sent
- 04Failure classification — distinguishing a model error, a tool error, a permission denial and a budget exhaustion
- 05Replay or resume — re-run from the start or continue from the failed step with corrected input
- 06Retention and export — how long traces are kept, and a way to export one for a support conversation
- 07Filtering by agent, status and date range
Resources that help you build this
12- AI Elements · Vercel's 47-component shadcn registry for chat, agent, voice and workflow UIs
- assistant-ui · React chat primitives and shadcn-installable UI for LLM apps, copilots, and agents
- OpenTUI · React, Solid and TypeScript renderers for terminal UIs, on a native Zig core
- React Bits Pro · 703 paid React items in one license-gated shadcn registry: 134 animated components, 538 blocks, 11 templates and an Agent Kit
- ReUI · 1,052 free shadcn components, 502 pro blocks, 10 templates, hosted MCP
- beUI · 76 React motion components and AI agent UI, installed through a shadcn registry
- brainless · Claude Code, Codex and Grok terminal UIs as shadcn components
- termcn · Terminal UI components for React, installed with the shadcn CLI, on Ink and OpenTUI
- Thinking Orbs · React canvas loading orb with nine agent states, two sizes and automatic dark/light
- Thinking Orbs · React canvas loading orb with 9 named agent states and two sizes
- Beautiful UI · 20 MIT interaction patterns for agent UIs: thinking, streaming, approvals, diffs
- nauvalazhar/ai · 48 owned-source React components for agentic AI apps, on Base UI + Tailwind v4