Dashboard tour

The bundled dashboard is the control surface for solo developers and the day-to-day operator view in team deployments. Launch the desktop app or run coro start (CLI install), then open http://localhost:3000/dashboard/.

Runs list

The Runs view is your queue of active and historical jobs. Each row surfaces status, repository, current phase, and quick links to logs. Use it to answer “what is running right now?” without tailing files.

Click New Run to enqueue work visually—see Your first job and Coro plan mode for the conversational brief flow and the classic form.

Run detail

Click a run to open its detail page. Typical sections include:

• Phase timeline — Where the job is in spec-writing, planning, coding, review, evaluation, or a parked state. Each phase node can show model/provider usage and posted artefacts.
• Logs — Streaming harness output and agent tool traffic (complements coro logs in the terminal).
• Artefacts — Per-phase outputs registered via post_artifact (plans, specs, PR links, evaluation reports). Markdown kinds such as spec-md, plan-md, and implementation-plan-md open in a rendered modal.
• Work items — Planner-authored breakdown; the merge gatekeeper advances these in order.
• Cost / usage — Aggregate signal for token spend (exact metrics depend on executor and tenant telemetry settings).
• Pull requests — Links back to your SCM; this is the human review surface the PR Reviewer coordinates.

Interactive jobs may show checkpoints where the harness waits for approval—those appear inline with phase state. The approval panel lets you continue, message the agent, or rerun a phase when supported.

Intelligence

The Intelligence area visualises how layers compose—base @coro-ai/intelligence-base, tenant overlay, and per-repo .coro/ additions. Use it when you wonder which markdown file wins after merges. The mental model is documented in Intelligence layers.

Tenant overlay wiring (Git remote, local intelligence directory) is configured under Settings → Advanced → Paths, not on this page.

Settings

Settings is where you configure authentication, integrations, guardrails, and runner paths. Everything here persists to ~/.coro/config.json when you click Save all changes—you do not need to edit that file by hand for normal operation.

Sections are grouped into three buckets:

General

Section	Purpose
Coach mode	Safer defaults for new users — interactive checkpoints on by default until you graduate (default after five dispatches)
Coro plan mode	Default New Run surface: conversational brief (ai), classic form (form), or Ask each time

Setup (required to run jobs)

Section	Purpose
LLM provider	Claude login, API keys, OpenAI, phase model aliases
Source control	GitHub, GitLab, Bitbucket credentials and test connection
Issue tracker	Optional Jira, Linear, or GitHub Issues

See Configure providers for detail on each Setup section.

Extensions (optional)

Section	Purpose
Plugins	Install and manage drop-in integrations
MCP servers	Bring-your-own MCP JSON + inherit Claude Code MCPs
Guardrails	PR description, diff size, merge approval, proposal policies

Advanced (rarely changed)

Section	Purpose
Paths	Intelligence directory, intelligence git remote (tenant overlay), working directory, config path reveal

Use Run setup wizard in the Settings header to replay first-time setup. Reload pulls the latest config from disk if you changed it externally.

New Run page

Runs → New Run (/dashboard/jobs/new) supports two intake surfaces. Both create the same Job as coro job.

Coro plan mode

• Header: page title, Use the form instead, and Back.
• Left column: chat — describe the task, see tool-use indicators when read-only lookups run.
• Right column: placeholder (“Your brief will appear here…”) until Coro emits a brief, then:
  • Run brief — editable repository, description, reviewers, workflow, interactive checkbox, and Start this run.
  • What will happen — phase timeline, duration band, and checkpoint summary for the selected workflow.
• Composer footer: model picker (Model: label), Force brief now, and send/stop controls.

See Coro plan mode for session limits and troubleshooting.

Classic form

• Header: Try Coro plan mode (when plan mode is available), Back.
• Left column: mode cards (manual vs ticket), form fields, Run options (interactive checkpoints switch), and collapsible Advanced → Workflow picker.
• Right column (desktop): sticky What will happen preview with phase timeline.
• Bottom bar: workflow name, Interactive and Autonomous dispatch buttons (or a single primary button when coach mode banner is off).

Recent repos and reviewers appear as suggestion chips below the classic form fields. Start from an example opens sample prompts you can drop into chat or the description field.

Cross-check Your first job, Coro plan mode, and Configure providers if a run stalls during provider resolution.