Agent Grid
ProThe fleet view: a card for every agent with its status and how long it has been in it, optionally selectable.
Playground
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Account research
Builds a one-pager on every new lead before the first call.
Contract review
Reads redlines and flags anything outside the playbook.
Renewals
Prepares renewal quotes 60 days before a contract ends.
Meeting notes
Writes up calls and posts the action items to the team.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Account research
Builds a one-pager on every new lead before the first call.
Contract review
Reads redlines and flags anything outside the playbook.
Renewals
Prepares renewal quotes 60 days before a contract ends.
Meeting notes
Writes up calls and posts the action items to the team.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Account research
Builds a one-pager on every new lead before the first call.
Contract review
Reads redlines and flags anything outside the playbook.
Renewals
Prepares renewal quotes 60 days before a contract ends.
Meeting notes
Writes up calls and posts the action items to the team.
Installation
Agent Grid comes with WunderUI Core and Pro, in the package from your plan. See the plans.
Then import what you need:
import { AgentGrid } from "@wunderui/react"Then use it:
import { useState } from "react"
import { AgentGrid } from "@wunderui/react"
export function Fleet() {
const [selected, setSelected] = useState("collections")
return (
<AgentGrid
columns={2}
selectedId={selected}
onSelect={(agent) => setSelected(agent.id)}
agents={[
{ id: "collections", name: "Collections", status: "waiting" },
{ id: "triage", name: "Inbox triage", status: "running" },
]}
/>
)
}Expected result: You should see two cards side by side, each with a bot icon, the name and a status pill. The first has an indigo border; press the second and the border moves to it.
When to use
Use Agent Grid for
- The overview of every agent you run, with a status and a live counter on each
- Choosing an agent to open in a detail pane, with the choice kept in your state
- A read-only wall of agents with a Run or Pause button on each card
Use something else for
- Run Timeline for the steps of one run, in order
- Agent Lane for parallel workers inside one run
- Agent Status for one status pill on its own, for example in a header
- List Group for a long, dense list of rows instead of cards
Columns
Columns sets the widest layout, from 1 to 4. The grid shows one column on a phone, two from the small breakpoint and up to your number from large, and it follows the window, so 4 needs a wide page.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Account research
Builds a one-pager on every new lead before the first call.
Contract review
Reads redlines and flags anything outside the playbook.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Account research
Builds a one-pager on every new lead before the first call.
Contract review
Reads redlines and flags anything outside the playbook.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Account research
Builds a one-pager on every new lead before the first call.
Contract review
Reads redlines and flags anything outside the playbook.
Content
Only a name and status are needed. The name stays on one line with an ellipsis, the description is clamped to two lines, and the meta line wraps next to the status.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Collections
Inbox triage
Quarterly revenue reconciliation and board report agent
Reconciles the ledger with the bank feed, flags every mismatch above $500 and drafts the summary for the board report before the monthly review.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Status
The status pill is Agent Status. A running or waiting agent counts up from its start, and a finished one shows the time since it ended.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
Tint
tint gives an agent an icon tile in a hue: a tint surface without a rim and the icon in the tint text of the same hue. Without it the tile is grey.
Release writer
Drafts the notes for every release.
Triage
Sorts new issues by area and risk.
Release writer
Drafts the notes for every release.
Triage
Sorts new issues by area and risk.
Keyboard interactions
Only a selectable grid has keyboard behaviour: each card is a button in the tab order and arrow keys do nothing. A read-only grid has no tab stops.
- TaborShift+Tab
- Moves focus from one card to the next, in reading order. Focus shows as an indigo border with a 2 px ring. A control in is a tab stop of its own.
- EnterorSpace
- Selects the focused card: is called with its agent and follows . Space does not scroll the page.
Behavior and motion
How the grid lays out its cards, how selection works and what the cards do on their own.
- Columns
- The column count is the widest layout: one column below 640 px, two from 640 px, the full number from 1024 px. Breakpoints follow the window width, not the grid's box.
- Selection
- You own the selection. The grid highlights the card whose id matches and calls your handler with the pressed agent; pressing the selected card does not clear it.
- Read only
- Without a selection handler a card is a plain box: no role, no tab stop, no hover fill. A selected id still draws the selected look, so a read-only grid can mark an agent.
- Status
- Running and waiting agents tick a counter from their start time once a second. A finished agent with a start time shows the time since then; without one there is no counter.
- Content
- The name is cut after one line, the description after two. The meta line wraps below the status on a narrow card, and cards in a row are as tall as the tallest.
- Action
- Clicks on the action area never reach the card. In a selectable grid that makes a button inside a button, so keep actions for read-only grids.
- Empty and loading
- The grid has no empty, loading or error state. With no agents it draws an empty grid; show your own state instead.
- Hover and press
- A selectable card fills with the page colour on hover and the subtle colour while pressed; the selected card keeps the subtle fill.
- Motion
- Only the running agent's status icon turns, and colours fade on hover and press.
- Reduced motion
- With reduced motion on, the running icon stands still; the status word and counter say the same.
Anatomy
The figure marks a grid of two cards with an action on each. The description has no number: it sits between the name and the status.
Collections
Chases overdue invoices and drafts the reminder emails.
Inbox triage
Labels incoming mail and answers the ones it is sure about.
- 1data-slot="agent-grid"
A grid with 12 px between cards: one column on a phone, two on small screens, up to four on wide ones.
- 2data-slot="agent-grid-item"
One agent in a bordered card with 16 px radius and padding. When selectable it can be pressed; the selected card has an indigo border and a subtle fill.
- 3Optional
The icon in a 36 px tile with a 12 px radius. Without one the tile shows a bot.
- 4
The name in 14 px semibold, on one line, cut with an ellipsis when long.
- Optional
The description in 13 px secondary text, clamped to two lines.
- 5Optional
A button or menu at the top right. Pressing it never selects the card.
- 6data-slot="agent-status"
A small Agent Status pill. A running or waiting agent counts up from its start time.
- 7Optional
A short fact in 12 px tertiary text next to the status, like 14 runs today. It wraps below the status on a narrow card.
Best practices
- Do
Set the start time to the moment the agent entered its current status. The pill counts from it, so nobody has to ask how long an agent has been stuck.
- Do
When the grid drives a detail pane, pass the selection handler together with the selected id. The selected card gets the indigo border and aria-pressed.
- Do
Keep the description to one sentence and put short facts in the meta line, such as 14 runs today.
- Do
Show a skeleton, an Empty State or an Alert instead of the grid while it loads, when there are no agents or when the request fails. An empty list draws nothing.
- Don’t
Don't combine selection and an action: a selectable card is a button, and a button inside a button is invalid. Use actions in a read-only grid, or put controls in the detail pane.
- Don’t
Don't expect arrow-key navigation. Every card is its own Tab stop; with many agents add a filter or search above the grid.
- Don’t
Don't expect a second press to clear the selection. Pressing the selected card calls the handler again with the same agent.
API reference
AgentGrid is a plain component, so the table lists every prop. Each agent entry is described below.
A grid with 12 px between cards: one column on a phone, two on small screens, up to four on wide ones.
| Prop | Type | Default | Description |
|---|---|---|---|
| agents required | AgentSummary[] | — | The agents to show, in order. Each one has an and a , a (, , , , or ) and optionally , (a Date, a timestamp or a date string), , and . An empty list draws nothing. |
| selectedId | string | — | The of the agent to draw as selected. It does not need . |
| onSelect | (agent) => void | — | Called with the agent that was pressed or chosen with Enter or Space. Passing it turns the cards into buttons. |
| columns | 1 | 2 | 3 | 4 | 3 | The widest layout, 1 to 4. Default 3. The grid shows fewer columns on narrower windows. |
| className | string | — | Extra classes for the grid, for example . |
Notes for AI
Give your coding assistant the Markdown reference instead of screenshots.
get_component("agent-grid")The full library index for assistants is at /llms.txt.
Related components
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
Idle1 queued · 0/min
- Capture the sidebar in dark modeQueued
AI & Agents3 stylesProAgent LaneOne parallel worker: its status, queue, throughput and the tasks it holds.- 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.