Agent monitor
Agent monitor is a Agents block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Watching one agent run, and giving it the OK when it asks
Anatomy
Ink header with the agent, its status, elapsed time and spend · a time strip sized by how long each step took · steps on a rail with the one at work on top · approval in the row with the command it will run · Next or a summary in the footer · pause, resume and stop
- Publish v3.2.0 on GitHub?0:01
The agent wants to publish the release with these notes.
gh release create v3.2.0 --target main --notes-file notes.md - 11.4sWrote the notes in four sections: new, improved, fixed and thanks.
- 4.1sMatched the closed issues in Cycle 32 to the commits that closed them.
- 6.2sListed every commit on main since the v3.1 tag and grouped them by pull request.
In the Orvain Library
Get Agent monitor for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Agents
What’s inside
06parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Ink headerwith the agent, its status, elapsed time and spend
- A time strip sized by how long each step took
- Steps on a railwith the one at work on top
- Approval in the rowwith the command it will run
- Next or a summaryin the footer
- Pause, resume and stop
Responsive behaviour
560 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Agents earns its place
Reach for Agents
- An agent that acts in other people's apps, where some of its actions need a yes before they happen.
- Several agents or several attempts running at once, where someone has to see which is stuck and which is done.
- Runs long enough that people leave and come back, and need to catch up on what happened and what waits on them.
- Spend or time that has to be explained afterwards, step by step, against a budget.
Reach for something else
- A single question and a single answer. An assistant thread from the AI Chat family is the right surface, with its research shown inline.
- A background job with no decisions in it, such as a nightly export. A progress bar and a notification say all there is to say.
- A fixed automation people design ahead of time. Build it on the Workflow canvas, where the steps are drawn before they run rather than chosen as it goes.
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Agent monitor” block to this page: ink header with the agent, its status, elapsed time and spend, a time strip sized by how long each step took, steps on a rail with the one at work on top, approval in the row with the command it will run, Next or a summary in the footer, pause, resume and stop.
Questions about Agent monitor.
What is the Agent monitor block?
Agent monitor is a Agents block from Orvain UI, built for React and Vue with a matching Figma frame. Best for watching one agent run, and giving it the OK when it asks.
What is the Agent monitor block made of?
6 parts: ink header with the agent, its status, elapsed time and spend; a time strip sized by how long each step took; steps on a rail with the one at work on top; approval in the row with the command it will run; next or a summary in the footer; and pause, resume and stop. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Agent monitor block responsive?
Yes. It is drawn at 560px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Agent monitor block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Agent monitor block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Agent monitor block to this page.”
When should I not use a Agents block?
A single question and a single answer. An assistant thread from the AI Chat family is the right surface, with its research shown inline.
More Agents blocks
All AgentsPremium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain MCPAgent monitor
Agent monitor is a Agents block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Watching one agent run, and giving it the OK when it asks
Anatomy
Ink header with the agent, its status, elapsed time and spend · a time strip sized by how long each step took · steps on a rail with the one at work on top · approval in the row with the command it will run · Next or a summary in the footer · pause, resume and stop
- Publish v3.2.0 on GitHub?0:01
The agent wants to publish the release with these notes.
gh release create v3.2.0 --target main --notes-file notes.md - 11.4sWrote the notes in four sections: new, improved, fixed and thanks.
- 4.1sMatched the closed issues in Cycle 32 to the commits that closed them.
- 6.2sListed every commit on main since the v3.1 tag and grouped them by pull request.
In the Orvain Library
Get Agent monitor for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Agents
What’s inside
06parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Ink headerwith the agent, its status, elapsed time and spend
- A time strip sized by how long each step took
- Steps on a railwith the one at work on top
- Approval in the rowwith the command it will run
- Next or a summaryin the footer
- Pause, resume and stop
Responsive behaviour
560 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Agents earns its place
Reach for Agents
- An agent that acts in other people's apps, where some of its actions need a yes before they happen.
- Several agents or several attempts running at once, where someone has to see which is stuck and which is done.
- Runs long enough that people leave and come back, and need to catch up on what happened and what waits on them.
- Spend or time that has to be explained afterwards, step by step, against a budget.
Reach for something else
- A single question and a single answer. An assistant thread from the AI Chat family is the right surface, with its research shown inline.
- A background job with no decisions in it, such as a nightly export. A progress bar and a notification say all there is to say.
- A fixed automation people design ahead of time. Build it on the Workflow canvas, where the steps are drawn before they run rather than chosen as it goes.
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Agent monitor” block to this page: ink header with the agent, its status, elapsed time and spend, a time strip sized by how long each step took, steps on a rail with the one at work on top, approval in the row with the command it will run, Next or a summary in the footer, pause, resume and stop.
Questions about Agent monitor.
What is the Agent monitor block?
Agent monitor is a Agents block from Orvain UI, built for React and Vue with a matching Figma frame. Best for watching one agent run, and giving it the OK when it asks.
What is the Agent monitor block made of?
6 parts: ink header with the agent, its status, elapsed time and spend; a time strip sized by how long each step took; steps on a rail with the one at work on top; approval in the row with the command it will run; next or a summary in the footer; and pause, resume and stop. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Agent monitor block responsive?
Yes. It is drawn at 560px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Agent monitor block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Agent monitor block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Agent monitor block to this page.”
When should I not use a Agents block?
A single question and a single answer. An assistant thread from the AI Chat family is the right surface, with its research shown inline.
More Agents blocks
All AgentsPremium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
