Agent Run Status

The top of a run: state, current step, a live clock, and Pause and Stop.

PROGet Agent Run Status and 168 other Pro components with pro lifetime — Get Pro

Category
AI Agent
Access
Pro
Source
435 lines · one file
States
7 drawn

The decision inside it

Segments, not a percentage

"Step 3 of 6" is a fact; "47%" of an agent run is a guess. The bar is one segment per step, and only becomes a plain bar past twelve.

When to use it

Use Agent Run Status as the header of a running agent: a turning ring, progress per step, a live clock and Pause, Resume, Stop and Run again. RunStatusBadge is the small status pill on its own, for tables and lists.

Installation

How you get it

Paste this into Claude Code, Cursor, Codex or any coding agent. It installs the file and uses it as it is, instead of writing a new one.

Use Liro's Agent Run Status for this.
Install it: npx shadcn@latest add @liro/agent-run-status
(the @liro registry is set up in components.json, with LIRO_KEY in .env.local)
Import it from @/components/ui/agent-run-status.
Do not rewrite or restyle it. Pass my data through its props
and keep its built-in states.

For the full brief with every prop and the mistakes assistants usually make, use Copy prompt above. Pro components install through the @liro registry with your CLI token: see the Namespaced tab.

Usage

components/run-header.tsx
import { AgentRunStatus, RunStatusBadge, type RunStatus } from "@/components/ui/agent-run-status";

export function RunHeader({ status, onStop, onRetry }: { status: RunStatus; onStop: () => void; onRetry: () => void }) {
  return (
    <div className="grid gap-3">
      <AgentRunStatus
        title="Chase unsigned agreements"
        status={status}
        step={{ index: 2, total: 5, label: "Checking signers" }}
        startedAt={Date.now() - 42_000}
        onStop={onStop}
        onRetry={onRetry}
      />
      <RunStatusBadge status={status} />
    </div>
  );
}

API reference

“Copy prompt” above puts a full brief on your clipboard, install command, dependencies, props, and the mistakes an assistant usually makes with this component.

Props

Read from the component’s own TypeScript interface when the site is built, so this table cannot drift from the file you install.

TypeNotes
statusRunStatus Yes–
labelReact.ReactNode NoReplaces the default word: "Needs you" for `waiting`, say.
size"sm" | "md" No–

Dependencies

npm packages

clsxframer-motionlucide-reacttailwind-merge

Liro foundations, installed alongside it

liro-themebadgebuttontooltip

States

All of them are drawn by the component. None is left for you to design.

  • Queued
  • Running
  • Needs approval
  • Paused
  • Completed
  • Failed
  • Stopped

Accessibility

  • Keyboard reachable throughout, in visual order
  • Focus trapped in overlays, Escape closes them
  • Focus returns to whatever opened it
  • Live regions announce what changed, not that something did
  • Honours prefers-reduced-motion

Responsive behavior

  • Sizes to its container, not the viewport
  • Usable from 320px up
  • Pointer-based interaction, so trackpad and touch both work
  • No hover-only affordances

Used in a screenAll screens

ScreenPro

Agent Run

One agent run, live: its plan, every tool call, a pause for approval and the finished output.