Agent Lane
ProOne worker of a run that fans out: its status, how much is queued, how fast it works and the tasks it holds.
Playground
Docs audit
Active3 queued · 42/min
- Checking page 38 of 122Running
- Screenshot dark modeQueued
Docs audit
Active0 queued · 42/min
Waiting for a free slot
Screenshots
Idle1 queued · 0/min
- Capture the sidebar in dark modeQueued
Screenshots
Idle0 queued · 0/min
Waiting for a free slot
Figma sync
Saturated18 queued · 96/min
- Binding 214 variablesRunning
- Rebuild the icon setsQueued
- +16 more waiting
Figma sync
Saturated18 queued · 96/min
Waiting for a free slot
Installation
Agent Lane comes with WunderUI Core and Pro, in the package from your plan. See the plans.
Then import what you need:
import { AgentLane, AgentLaneStatus, AgentLaneTask } from "@wunderui/react"Then use it:
import { AgentLane } from "@wunderui/react"
export function DocsAudit() {
return (
<AgentLane
name="Docs audit"
status="active"
queue={3}
throughput={42}
tasks={[
{ title: "Checking page 38 of 122", state: "Running" },
{ title: "Screenshot dark mode", state: "Queued" },
]}
/>
)
}Expected result: You should see a card with an indigo dot, Docs audit and Active, the line 3 queued, 42/min, and two task chips with their states under it.
When to use
Use Agent Lane for
- One worker of a run that fans out, shown next to the others
- A snapshot of where work piles up: the queue, the rate and the tasks in hand
- A lane that says in words whether it is active, idle or saturated
Use something else for
- Agent Grid for agents as cards in a grid, each with its own run
- Run Timeline for the steps of one run over time, with duration and result
- Agent Status for one pill that says what a run is doing right now
Tasks
A lane lists the tasks it holds as chips. When more wait than the chips show, a line such as +16 more waiting is added, and a lane with no tasks says so in text you can replace.
Docs audit
Active3 queued · 42/min
- Checking page 38 of 122Running
- Screenshot dark modeQueued
Figma sync
Saturated18 queued · 96/min
- Binding 214 variablesRunning
- Rebuild the icon setsQueued
- +16 more waiting
Screenshots
Idle0 queued · 0/min
Waiting for a free slot
Screenshots
Idle0 queued · 0/min
Run cancelled. 3 tasks were not started.
Metrics
Under the name the lane shows how many tasks are queued and how many it finishes per minute. Without a rate it shows a dash and zero shows 0/min, and numbers print as given.
Docs audit
Active3 queued · 42/min
- Checking page 38 of 122Running
- Screenshot dark modeQueued
Docs audit
Idle3 queued · 0/min
- Checking page 38 of 122Queued
Docs audit
Active3 queued · —
- Checking page 38 of 122Running
- Screenshot dark modeQueued
Task
A task is a one-line title with an optional state under it. A longer title ends in an ellipsis, and the state can be text or an element, which is how a failed task is shown.
Docs audit
Active3 queued · 42/min
- Checking page 38 of 122Running
- Screenshot dark modeQueued
Docs audit
Active3 queued · 42/min
- Checking page 38 of 122
- Screenshot dark mode
Docs audit
Active3 queued · 42/min
- Checking /components/data-table for contrast, focus order and the reduced motion fallbackRunning
- Screenshot dark modeQueued
Docs audit
Active3 queued · 42/min
- Checking page 38 of 122Failed: timed out after 30 s
- Screenshot dark modeQueued
Behavior and motion
What the lane draws, what it leaves to you, and how it behaves for assistive technology and motion.
- Structure
- A section named by the lane's name, with tasks as a list and the more line as one more list item. The lane keeps no state or timers: every number and word comes from props.
- Status
- Each status changes the dot and the colour of the status word, and the word is always written out. The lane applies no rule of its own: it is saturated when you say so.
- Metrics
- The line shows the queue and the rate per minute, printed as given, so 1842 has no thousands separator. Without throughput the rate is a dash; 0 shows 0/min.
- Tasks
- Each task is a chip with a one-line title and an optional state. Titles end in an ellipsis with no tooltip; the more line shows only next to tasks, otherwise the empty text.
- Failure and abort
- There is no failed or cancelled status. A failed task is text in its state and a stopped lane is idle; after an abort give each lane an empty text like Stopped, 9 tasks were not started.
- Time
- A lane is the present: it has no time axis and no history of earlier runs. For a run over time use Run Timeline.
- Selection and keyboard
- The lane is not interactive: no focus, hover, press or selected style, and no key does anything on it. A button stretched over the lane adds selection, as in the Examples tab.
- Motion
- The lane has no animation or transition. A queue that changes is redrawn at once.
- Reduced motion
- Nothing moves, so there is nothing to reduce. Every state is written as text as well as colour.
Anatomy
The figure marks a lane with two tasks and more waiting. The empty text replaces the task list and has no number.
Figma sync
Saturated18 queued · 96/min
- Binding 214 variablesRunning
- Rebuild the icon setsQueued
- +16 more waiting
- data-slot="agent-lane"
A section named by the lane's name, with a 1 px border and 16 px radius. It is not interactive: no role, no tab stop, no hover.
- 1
An 8 px dot, hidden from assistive technology. Indigo for active, grey for idle, yellow for saturated.
- 2
The name in 14 px semibold, on one line with an ellipsis. It names the section.
- 3
Active, Idle or Saturated as visible text in the status colour, so the status is never colour alone.
- 4
One line such as 18 queued and 96/min, in tabular numbers. The rate shows a dash when there is no throughput.
- 5Optional
A list item on a subtle tint with an 8 px radius: the title on one line with an ellipsis, and the state under it if there is one.
- 6Optional
A last list item such as +16 more waiting, shown when the more count is above zero and the lane has tasks.
- Optional
Shown in place of the task list when there are no tasks. The default is Waiting for a free slot.
Best practices
- Do
Set the status from the real queue. The lane draws what it is told and applies no threshold, so decide yourself when a lane counts as saturated.
- Do
Pass the running task first, then the queued ones, and use the more count for the rest. Keep queue and more consistent: the lane does not derive one from the other.
- Do
Show a failure as text in the task's state, in the red tint, and leave the lane idle if it stopped. There is no failed status.
- Do
Show an aborted run as idle with a queue of 0 and an empty text that says how many tasks were not started.
- Do
Give every lane its own name. A lane is a named section, which is a landmark, and lanes with the same name cannot be told apart.
- Do
Lay lanes out in an auto-fit grid with a minimum width, say 180 px. A lane fills the width its parent gives it.
- Don’t
Don't expect it to take focus or a click. For a lane people can choose, put a button over it, as the Examples tab does.
- Don’t
Don't expect to read a long task title: it ends in an ellipsis after one line, with no tooltip. Show the full title elsewhere.
- Don’t
Don't pass the more count without tasks. The lane shows the empty text instead and the number is not drawn.
API reference
AgentLane is a plain component, so the table lists every prop.
A section named by the lane's name, with a 1 px border and 16 px radius. It is not interactive: no role, no tab stop, no hover.
| Prop | Type | Default | Description |
|---|---|---|---|
| name required | ReactNode | — | The name of the lane, one line with an ellipsis. It also names the section for assistive technology. |
| status required | "active" | "idle" | "saturated" | — | (indigo), (grey) or (yellow). The lane draws it and decides nothing; the word is written next to the dot. |
| queue required | number | — | How many tasks wait in this lane, a number printed as it is (). |
| throughput | number | — | Tasks per minute, a number printed as . Left out, the lane shows a dash; shows . |
| tasks | AgentLaneTask[] | [] | The tasks to show as chips, each with a , an optional (text or an element) and an optional used as the key. Empty by default. |
| more | number | — | How many tasks are not shown as chips, drawn as . Only drawn when the lane has tasks and the number is above zero. |
| emptyLabel | ReactNode | "Waiting for a free slot" | Shown when is empty. Default . |
| className | string | — | Extra classes for the card, for example a hover fill or for a selected lane. A width comes from the parent. |
Notes for AI
Give your coding assistant the Markdown reference instead of screenshots.
get_component("agent-lane")The full library index for assistants is at /llms.txt.
Related components
Collections
Chases overdue invoices and drafts the reminder emails.
Waiting for you14 runs todayInbox triage
Labels incoming mail and answers the ones it is sure about.
Running$2.10 todayAccount research
Builds a one-pager on every new lead before the first call.
Done6 runs todayContract review
Reads redlines and flags anything outside the playbook.
Failed3 failures this weekAI & Agents4 stylesProAgent GridThe fleet view — every agent, its current status and how long it has been there.- Done420 tok$0.01640ms
Input
status: overdue, age: 30+ daysOutput
14 invoices, $42,860 in total - Done3,420 tok$0.042.1s
Input
14 invoice idsOutput
14 contacts, all with an email address - Running2,310 tok
Input
template: invoice-overdue-30 - Pending
Input
to: 14 recipients - PendingLog the result
AI & Agents5 stylesProRun TimelineEvery step of a run in order, with duration, tokens and expandable input/output.