# Run Outcome Report block

> Agent run outcome report with a done, failed or skipped badge per item and a scoped retry

Wrap-up card for a finished agent task: the command, record or reason behind each row, a Grant button for a missing scope, and Keep what succeeded with undo. Built on ReUI Frame, Badge, shadcn Item, ButtonGroup. For run summary, task results.

- 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-5
- MCP: `get_block("agent-activity-5")`
- Built with: Badge, Button, Button Group, Dropdown Menu, Frame, Item, Skeleton, Spinner, Tooltip
- Installs with a ReUI Pro or Ultimate license; setup: https://web.dev.reui.io/docs/license-setup

## Best for

A settled run's ledger marking unchecked successes Unsupported and rerunning skipped items once their blocker recovers, with Discard

## Agent notes

- Replace `OUTCOME` and `ITEMS`; the retry is simulated, as `resolveRetry` swaps in each item's `recovered` result after `RETRY_MS`
- The Grant issues:create button only calls `clearBlocker`, which drops `needsYou` locally and fires a `toast`; no scope is granted
- Full activity only fires a `toast`, and Discard, Restore run and Keep what succeeded change only local `discarded`, `retrying` and `items` state

## When not to use

- Failed runs across a whole fleet triaged in a grid, with a retry ladder per run: use [Failed Run Triage](https://web.dev.reui.io/blocks/solutions/agents/solution-agents-7.md) (`get_block("solution-agents-7")`)
- A run still under way, held at an approval step until a person decides: use [Approval Run Console](https://web.dev.reui.io/blocks/ai-agents/agent-activity/agent-activity-1.md) (`get_block("agent-activity-1")`)

## 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-5
```

## 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.