affectUI › Components › Agents

Agent Workbench

One agent at work: the person who asked on the left with their message, the agent in the middle with a work area showing what it does right now, the files it was given on the right under a macOS folder, and its tools below as cards with what each may do and what it did last – joined by soft rounded connectors, with a light running along the one in use.

Part of affectUI Pro. Install: npx shadcn@latest add https://www.affectui.com/r/agent-workbench.json · Import from @/components/ui/agent-workbench

When to use

  • Showing one agent at work on one request: who asked, what it reads, which tools it calls and what it does right now
  • An assistant that works across a person's apps – mail, calendar, files – where people should see what it touches
  • A live view next to a chat, or a still picture of how an agent is wired up

When not to use

  • Many agents handing work to each other – use Agent Crew or Agent Tree
  • What an agent remembers and every tool it can reach – use Memory Graph
  • Each tool call with its input and output – use Agent Tool Calls

Usage

import { AgentWorkbench, type WorkbenchStep, type WorkbenchTool } from "@/components/ui/agent-workbench";

const tools: WorkbenchTool[] = [
  { id: "gmail", name: "Gmail", logo: <GmailLogo />, scope: "Read & send · ryan@lumen.co", last: "Sent the weekly digest", when: "2h ago" },
  { id: "calendar", name: "Google Calendar", logo: <CalendarLogo />, scope: "Read & book · Work" },
];

const steps: WorkbenchStep[] = [
  { id: "s1", text: "Reading Ryan's request", at: "user" },
  { id: "s2", text: "Checking Marc's calendar next week", at: "calendar", running: true },
];

export function Workbench() {
  return (
    <AgentWorkbench
      user={{ name: "Ryan Brooks", photo: "/ryan.jpg", message: "Find 30 minutes with Marc next week." }}
      agent={{ id: "assistant", name: "Assistant", subtitle: "Works in your Google account" }}
      tools={tools}
      files={[{ id: "budget", name: "budget-q4.xlsx", logo: <ExcelLogo />, meta: "48 KB" }]}
      steps={steps}
    />
  );
}

Props

NameTypeDefaultDescription
user{ name, message, photo?, avatar? }Who asked, on the left – their photo URL shown round beside the name (avatar takes your own node instead), and their message; without a photo, or if it doesn't load, the person's full mark
agent{ id, name, subtitle?, details? }The agent in the middle – its pixel mark from its id, twinkling while it works; click it and its info card opens below with details, what it does now, its steps and the tools it used
toolsWorkbenchTool[]Its tools below as cards – logo, name, what each may do and where, and what it did last; up to four, with more the last spot sums up the rest ("+3 more tools")
WorkbenchTool.scope / last / whenstring / string / string"Read & send · ryan@lumen.co", its last action and when – while it's called, what it does now shows instead
WorkbenchTool.details / WorkbenchFile.details{ label, value }[]Lines in the info card that opens below a tool or a file when it's clicked – a tool's card also lists what it did for this request
filesWorkbenchFile[]What it was given, on the right under a macOS folder – name, logo and a short meta like "48 KB"; up to four, then "+N more"; a file without a logo gets a plain page
stepsWorkbenchStep[]What it did and does, oldest first – the last three show in its work area, newest on top
WorkbenchStep.at / runningstring / booleanWhere it reaches – a tool id, "files" or "user" – and whether it still runs; the running step's line carries the light
readingstringThe id of the file it reads right now – lit up in the list
donebooleanFinished – the status says Done and nothing runs
titlestringThe section's accessible name
classNamestringExtra class on the root – set the color variables on it

Accessibility

  • The work area is a list with a polite live region – each new step is read as it comes in
  • Every card is plain text and logos marked decorative; the connectors and their dots are hidden from screen readers
  • Status is said in words – Working, Done, Calling, Used, Ready – never by color alone
  • The agent, every tool and every file is a button with its name and "details" – Enter or Space opens its info card, aria-expanded says it's open
  • One info card at a time; clicking it again, clicking outside or Esc closes it, and Esc puts focus back on the button
  • A focus ring shows only for the keyboard

Responsive

  • Fills its container's width – the person, the agent and the files in a row, the tools in a row below, joined by soft rounded connectors with a hollow dot at each end
  • Below 720px everything stacks – the person, the agent, the files, then the tools – and the connectors step aside
  • Long names, scopes, file names and steps end in … with the full text on hover; the message keeps to four lines
  • Broken data holds: a photo that doesn't load shows the person's mark, a step without text says Working… or Done, a tool without a last action says Nothing yet, no steps at all reads Waiting for a request
  • One or two tools stay card-sized in the middle instead of stretching across
  • The classic style has rounder cards, pill tags and status and firmer type – the same behavior as the clean one
  • The work area keeps three rows of the same height, so the card never jumps as steps come in
  • Dark mode built in: switches when an ancestor (usually <html>) has the class dark or data-theme="dark"

Requirements

  • React 19

Related

  • Agent Crew – A lead and its sub-agents as one live tree of cards – every agent stays on screen; each card says what the agent does right now, how full its context is, its tools and the last thing it was handed, and handoffs run as a light along Agent Tree's rounded connectors and light up the card they reach; a click on a card opens its task, model, usage and tools with actions to steer it, and a switcher swaps between projects
  • Memory Graph – An agent in the middle with what it remembers and the tools it can reach in a ring around it – every memory a card with the file, chat or email it came from and that app's logo, every tool with what it may do and where, joined by Agent Tree's rounded connectors; a light runs out to each tool it uses and in from a tool through the agent to what it learns, lighting the card up with a Gradient Floor; switch anything off, forget a memory, or click the agent to drop in a file or connect a tool
  • Agent Tree – Who started whom – an orchestrator and its sub-agents as a live tree, with status, cost and time on every card, costs rolling up each branch, and branches that fold to one line
  • Reasoning Summary – How an agent spent its time on one answer, in one small card – the agent's pixel mark twinkling while it reasons and the time counting, a bar with a segment per step in its kind's color, the running one growing with a sheen, the time per kind with its icon, and the models that took part with how hard they thought – click one for its provider, tokens and cost. Point at a kind, model or segment and what belongs with it stays clear; the sources it searched and every step open below