> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remyx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reports

> The fleet in one view: what your agents produced, where pools are depleting, and what's waiting on you

**Nav:** Reports | **URL:** [`/reports`](https://studio.remyx.ai/reports)

Reports is the fleet dashboard: what your agents produced, where pools are depleting, and what's waiting on you. It opens with a written **headline** — a one-line thesis about the window — then a **KPI strip** and **findings**, each finding deep-linking into the agent evidence it came from.

<Frame>
  <img src="https://mintcdn.com/remyxai/2lznviOD5A07VqzC/images/studio/reports-overview.png?fit=max&auto=format&n=2lznviOD5A07VqzC&q=85&s=d3b7d804742d918c3df97c4fde0be631" alt="The Reports dashboard: headline '15 drafts opened and 6 merged and 6 leads routed to discussion', a KPI strip with dispatches, drafts opened, merged, leads, needs-attention, and spend with cost per artifact, findings that deep-link to agent evidence, and the fleet-activity chart stacked by outcome kind per day" width="1920" height="962" data-path="images/studio/reports-overview.png" />
</Frame>

Two controls scope everything and ride the URL (so any view is shareable):

* **Agent picker** — all agents or a subset; the scope carries into every chart and drill-down.
* **Date window** — the same window control as agent views, from 7 days to All time.

A **↻ Refresh** button pulls the latest agent state from GitHub and rebuilds the report; the "Updated N minutes ago" stamp tells you how fresh the data is.

***

## Fleet activity

A daily stacked-bar chart of run volume by outcome kind — Draft PR / Discussion / Branch / Skipped / Failed — with spend overlaid. Legend chips toggle outcome kinds; zoom presets narrow to the last 90/30/14/7 days.

***

## Deliverable pipeline

Everything currently in flight, as cards: drafts and discussions with title, repo, age, and a direct **Open ↗** link. This is the maintainer-facing work the fleet has put in front of you, in one place.

***

## Per-agent breakout

Each agent classified into one of six states, filterable by chips (the summary counts how many **need attention** — blocked plus saturated):

| State         | Meaning                                                                  |
| ------------- | ------------------------------------------------------------------------ |
| **blocked**   | Runs are failing — something needs fixing                                |
| **saturated** | The candidate pool is exhausted — widen the interest or retire the agent |
| **shipped**   | Work merged in the window                                                |
| **active**    | Running normally                                                         |
| **new**       | Recently provisioned                                                     |
| **retired**   | Deliberately wound down                                                  |

Two views of the same data:

* **Outcomes** — proportional stacked bars per agent, scaled either absolute (bar length by busiest agent) or as share (100% rows).
* **Timeline** — a **contribution grid**: one cell per day (per week on long windows), colored by the highest-signal outcome that day and shaded by run count. A season of agent work reads at a glance, like a GitHub contribution graph for your fleet.

<Frame>
  <img src="https://mintcdn.com/remyxai/2lznviOD5A07VqzC/images/studio/reports-per-agent-breakout.png?fit=max&auto=format&n=2lznviOD5A07VqzC&q=85&s=a0d2a39203bd31980da9522813933ee7" alt="The per-agent breakout in Outcomes view, share scale: one 100% stacked bar per agent splitting its runs across draft PRs, discussions, and branches, with state filter chips (All 64 / shipped 12 / active 17 / new 35) and each agent's state labeled at the row's end" width="1695" height="624" data-path="images/studio/reports-per-agent-breakout.png" />
</Frame>

Sortable by status, name, run count, draft count, draft share, or failure share. A **Chronology** fold lists the discrete events — Enabled, Retired, Merged, Draft, Discussion — each linked to its artifact.

***

<h2 id="costs">
  Costs
</h2>

The **Spend** KPI drills into `/reports/costs` (carrying your window and agent scope): unit economics for the fleet. Runs per day stacked by model backend — toggle between one series per provider or per model — against a \*\*$ per code artifact** line, plus per-backend "$ / artifact" KPIs. Runs carry their backend, model, and tier (main / drafter / refiner), so a [two-tier setup](/platform/agents/backends#the-two-tier-drafter-refiner-pattern) shows exactly what exploration costs versus promotion.

***

## Programmatic access

The same report is available from the [MCP server](/resources/mcp-server#outrider-fleet-tools) (`get_fleet_report`) and the REST API (`GET /outrider/agents/report`), scoped to your own agents.

***

## Related

<CardGroup cols={2}>
  <Card title="Inbox" icon="inbox" href="/platform/review/inbox">
    The action items behind "needs attention"
  </Card>

  <Card title="Agents" icon="robot" href="/platform/agents/overview#the-agent-report">
    Drill into one agent's runs, direction, and trace
  </Card>

  <Card title="Model backends" icon="microchip" href="/platform/agents/backends">
    What drives the cost-per-artifact differences
  </Card>

  <Card title="Projects" icon="folder" href="/platform/configure/projects">
    Scope the fleet to an initiative
  </Card>
</CardGroup>