Skip to main content
Review the work Remyx ran and the evidence it returned.

Validation results

Reports → Validations shows linked pull requests, evaluation questions, outcomes, artifacts and costs. Validate works independently of Outrider, so a PR validation does not require an Outrider installation.
Studio Reports → Validations showing the SAELens PR with a pass result, linked spec, run history, and spend.

Studio Reports records PR validation outcomes and associated compute spend.

A passing offline result means the required criteria were met in that evaluation. It does not establish production impact. Results and evidence

Validations

URL: /reports/validations The Validations view records the repository, pull request, question, result, artifacts, and cost of each run. Use the date window to narrow the results. Production comparisons appear only when the corresponding signals have been recorded. A repository’s spec card shows its current .remyx/validation.yaml, associated runs, and a linting editor. Open a PR proposes spec edits on a new branch as remyx-ai[bot]; the default branch does not change until that PR merges. Without an entitlement (no free validation left, no balance, no grant) the page shows Validate is a paid feature with a link to Billing.

Outrider activity

Review selected candidates, published drafts, held changes, and execution outcomes across configured repositories. Nav: Reports | URL: /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.
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
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): 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.
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
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.

Insights

Below the findings, Insights groups the window’s work into named idea clusters, each with a verdict, under four headers: A standouts list calls out the single findings worth reading first. Every cluster links to the artifacts behind it.

Costs and history

Use the available filters and run records to inspect activity and spend for the relevant period.

Costs

The Spend KPI reads median XperopenedPR/issue(N)⋅X per opened PR/issue (N) · Y overhead: the median cost of the runs that produced an artifact, and what the runs that produced none added up to. It drills into /reports/costs (carrying your window and agent scope): unit economics for the fleet. Runs per day stacked by series, with grain chips for Agent (the coding-agent CLI), Provider (the model backend), or Model (each provider split down to its models), against a cost-per-artifact line and per-series KPIs. Runs carry their coding agent, backend, model, and tier (main / drafter / refiner), so a two-tier setup shows exactly what exploration costs versus promotion. A run whose agent reports no dollar figure is left out of spend rather than counted as $0, and the number of those runs rides along — so a partial total says so instead of quietly understating.

Programmatic access

The same report is available from the MCP server (get_fleet_report) and the REST API (GET /outrider/agents/report), scoped to your own agents.

Production outcomes

When production signals have been connected and recorded, Reports can compare later outcomes with offline validation results. The presence of an offline result alone does not supply production evidence.

Inbox

The action items behind “needs attention”

Agents

Drill into one agent’s runs, direction, and trace

Model backends

What drives the cost-per-artifact differences

Projects

Scope the fleet to an initiative