Agent Lanes

A live timeline with a lane per agent, hand-offs between them and approvals on the block.

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

Category
AI Agent
Access
Pro
Source
548 lines · one file
States
7 drawn
Added
21 Oct 2026

The decision inside it

Idle time is drawn as idle

A timeline that only draws work makes a blocked team look busy. Gaps say "idle 4m", and a lane waiting on a person becomes a striped Waiting on you block that keeps growing, the first thing a manager needs to see.

When to use it

Use Agent Lanes for a live view of several agents at once: a lane each, blocks that grow into now, hand-offs between agents, idle gaps and approvals right on the block. For a parent-child view use Sub-agent Tree.

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 Lanes for this.
Install it: npx shadcn@latest add @liro/agent-lanes
(the @liro registry is set up in components.json, with LIRO_KEY in .env.local)
Import it from @/components/ui/agent-lanes.
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/team-lanes.tsx
import { AgentLanes, type LaneAgent, type LaneTask } from "@/components/ui/agent-lanes";

const agents: LaneAgent[] = [
  { id: "research", name: "Research", role: "Finds sources" },
  { id: "writer", name: "Writer", role: "Drafts the brief" },
];

export function TeamLanes({ tasks, approve, reject }: {
  tasks: LaneTask[];
  approve: (id: string) => Promise<void>;
  reject: (id: string) => Promise<void>;
}) {
  return <AgentLanes agents={agents} tasks={tasks} window={10 * 60_000} onApprove={approve} onReject={reject} />;
}

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
agentsLaneAgent[] Yes–
tasksLaneTask[] Yes–
windownumber NoHow much time fits the width, in ms. Default 10 minutes. Controlled.
defaultWindownumber No–
onWindowChange(ms: number) => void No–
onApprove(taskId: string) => void | Promise<void> NoMay return a promise.
onReject(taskId: string) => void | Promise<void> NoMay return a promise.
onSelect(taskId: string) => void No–
nowDate | number NoFix the clock, for screenshots and tests.
lookLook NoLayered sets it in a tray, the heading above the card and the status in the strip below. Flat is one card.

Dependencies

npm packages

clsxframer-motionlucide-reacttailwind-merge

Liro foundations, installed alongside it

liro-themebutton

States

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

  • Live
  • Waiting on you
  • Idle
  • Hand-off
  • Failed
  • Zoomed
  • Scrolled back

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

Multi-agent Chat

A chat with the agent running a job, the agents it handed work to, and the brief, side by side.