# Approval Run Console block

> Agent run console that stops at approval steps for an inline Approve, Revise or Deny

Human in the loop task view: queue badges on steps that will need you, an answer field for agent questions, and a declined approval skipping its gated steps. ReUI Frame, Badge, shadcn Marker, Progress, InputGroup. For approval flow, run log.

- Type: Pro block
- Category: [Agent Activity](https://web.dev.reui.io/blocks/ai-agents/agent-activity.md)
- Page: https://web.dev.reui.io/blocks/ai-agents/agent-activity/agent-activity-1
- MCP: `get_block("agent-activity-1")`
- Built with: Badge, Button, Dropdown Menu, Frame, Input Group, Marker, Progress, Spinner, Tooltip
- Installs with a ReUI Pro or Ultimate license; setup: https://web.dev.reui.io/docs/license-setup

## Best for

A run that stops for a person, flagging High impact approvals in the queue ahead, with Revise notes and a fold for finished steps

## Agent notes

- Replace `RUN` and `RUN_META`; a step's `gatedBy` names the approval whose Deny or Revise skips it, and `START_AT` of 2 opens the console mid run
- `decide` keeps Approve, Revise, Deny and typed answers in local `decisions` state only; send each decision and its note to your agent
- The Open file, Open link and Open console row actions only fire a `toast`; Copy Summary writes the `copyRun` text to the clipboard

## When not to use

- Pending actions from many runs, approved or rejected in bulk by risk tier: use [Action Approval Inbox](https://web.dev.reui.io/blocks/solutions/agents/solution-agents-5.md) (`get_block("solution-agents-5")`)
- A run nobody has to approve, watched in a raw log view and stopped at will: use [Live Run Feed](https://web.dev.reui.io/blocks/ai-agents/agent-activity/agent-activity-2.md) (`get_block("agent-activity-2")`)

## Third-party libraries

- Sonner v2: [API reference](https://sonner.emilkowal.ski/toast), [docs](https://sonner.emilkowal.ski/getting-started)

## Install

```bash
npx shadcn@latest add @reui/agent-activity-1
```

## About Agent Activity blocks

### When to use

- A live step feed of one agent run that the person who started it can approve, pause or stop
- The research trail behind an answer: the search query, numbered sources, repo files and confidence
- A record of what a run touched and settled: MCP calls per server, refused scopes and failed items

### When not to use

- Operator pages across many runs: a run queue, an approval inbox or tool access settings: use the [Agents blocks](https://web.dev.reui.io/blocks/solutions/agents.md)
- The conversation around the run: the message thread, the prompt composer and the replies: use the [AI Chat blocks](https://web.dev.reui.io/blocks/ai-agents/ai-chat.md)
- A dated history of what people did, such as activity feeds, milestones or release notes: use the [Timeline blocks](https://web.dev.reui.io/blocks/application/timeline.md)

### Agent notes

- Each page.tsx pads a top aligned `min-h-svh` wrapper around `AgentActivity`, whose root caps at `max-w-xl` or `max-w-2xl`; drop the wrapper in your layout
- Each run is replayed from the block's data file on `setTimeout` timers; drive the same state from your agent's events instead
- Each block calls `toast` from `sonner` but mounts no toaster, so those messages stay hidden until your layout renders one

Every ReUI item has a twin like this one; the index is https://web.dev.reui.io/llms.txt. Agents with the ReUI MCP (https://web.dev.reui.io/docs/mcp) get the same guidance from the getters named above.
