The dashboard is a local web UI that gives you a live view of your project's
health, tool usage, and memories. It runs as a separate process — no MCP server,
no LSP, no tool machinery — just the data already on disk in .codescout/.
codescout dashboard --project .
# opens http://127.0.0.1:8099Project health at a glance:
- Project — root path, detected languages, entry points
- Configuration — active settings from
.codescout/project.toml - Semantic Index — chunk count, last-indexed commit, staleness relative to HEAD
- Drift — files with high semantic drift since last index (files where meaning changed significantly, not just bytes)
- Libraries — registered third-party libraries and their index status
Usage telemetry for every tool call the MCP server has handled:
- Summary — total calls, error rate, overflow rate for the selected window
- Calls by Tool — bar chart ranked by call volume
- Per-Tool Breakdown — table with calls, errors, Err%, overflows, Ovf%, p50 and p99 latency
- Recent Errors — last N errors with full input/output, searchable and collapsible by duplicate group
The time window selector covers 1h / 24h / 7d / 30d and updates all panels simultaneously.
Read and edit the project's persistent memory store directly in the browser:
- Browse topics in the sidebar
- View raw markdown content
- Create, update, or delete topics without touching the filesystem manually
| Flag | Default | Description |
|---|---|---|
--host |
127.0.0.1 |
Bind address |
--port |
8099 |
Port |
--no-open |
off | Disable auto-opening the browser |
codescout dashboard --project . --port 9000- The dashboard reads
.codescout/directly; the MCP server does not need to be running - Static assets (HTML, CSS, JS) are embedded in the binary — no separate serving step
- Theme toggle (light/dark) persists across page loads via
localStorage
- Memory Tools — the
memorytool that backs the Memories browser - Semantic Search Tools —
project_statusis the data source for the index health and drift panels on the Overview page - Workflow & Config Tools — usage data from
.codescout/usage.dbbacks the Tool Stats page - Project Configuration — the Overview page shows your active configuration from
.codescout/project.toml