Your local context dashboard.

Open the dashboard

Run this from the project you want to inspect:

lean-ctx dashboard

LeanCTX starts a local web server, normally at http://localhost:3333, and opens your browser. Use the Browser URL printed in the terminal: with authentication enabled it includes the access token. Keep that URL private. Leave the terminal running; Ctrl+C stops that foreground dashboard process.

The same command works in PowerShell, Bash and zsh. If you installed through npm on Windows and PowerShell blocks the script shim, use lean-ctx.cmd dashboard. Native Windows, macOS and Linux installation paths are explained in Platforms & paths.

To select a project explicitly or avoid opening a browser:

lean-ctx dashboard --project="." --port=3334 --open=none

These options use --name=value, including --project and --port. Use an absolute project path when launching from another directory. --no-open is an alias for --open=none; neither option disables the server or authentication.

Find the right view

The cockpit opens in Simple mode. Switch to Advanced to reveal the topic areas and their tabs. Advanced is a navigation mode, not a paid plan.

Area	What you can inspect	What to keep in mind
Home	Runtime status, recent context activity and usage summaries	Results reflect activity observed by this installation.
Context	Context contents, live activity, compression comparisons and quick settings	Context-window contents may be estimates; request telemetry is a separate source.
Memory	Project knowledge, episodes, search and connected-agent activity	Retained knowledge is not automatically inserted into every model request.
Protection	Guard diagnostics, context-risk signals and policy views	A coverage view is not proof that every read was scanned or every threat detected.
Proof	Local cost/usage views, task outcomes, snapshots and trends	Separate estimated savings, measured provider usage and evaluated task quality.
Project Map	Dependencies, symbols, callers, routes, file tree and architecture	Build the relevant indexes; static extraction can miss dynamic behavior.

The dashboard reflects the connected Engine, identity and deployment profile. An Agents, ROI or policy panel is an inspection surface; a displayed score or event does not establish task success or a compliance certification. Consult versions and compatibility for interface boundaries.

Inspect one real operation

1. Open the dashboard for your project and choose Context → Live Activity.
2. In another terminal or your connected AI tool, make a read such as lean-ctx read README.md -m signatures.
3. Inspect the available activity and compression details. Recover full source if the abbreviated result does not answer the question.
4. Use observability to interpret counts and compare equivalent tasks.

Empty panels can mean no relevant activity was captured yet, a different project is selected, or the required index/integration is unavailable. A blank panel is not a measured zero-cost result.

Open inside your editor

lean-ctx dashboard --vscode

--open=vscode is equivalent. Supported editor detection includes VS Code, Cursor, VSCodium and Windsurf. The LeanCTX editor extension handles the native tab. If the handoff is unavailable, the command prints instructions; it does not silently open the external browser instead.

Export a report

lean-ctx dashboard --export --output=leanctx-report.html

This writes a standalone HTML report; it is not a live dashboard or a screenshot of every cockpit panel. Add --open to open the exported file. Review source paths, project details and measurements before sharing an export.

Configure access deliberately

Authentication is enabled by default, including on loopback. Follow the printed authenticated URL or the dashboard’s token prompt. Do not disable authentication to solve an expired or missing browser token.

Setting	Effect
--host=127.0.0.1, --port=3333	Explicit local bind and port; otherwise LEAN_CTX_HOST and LEAN_CTX_PORT can override defaults.
--base-path=/dashboard	Mount behind a reverse-proxy subpath; LEAN_CTX_DASHBOARD_BASE_PATH is the environment alternative.
LEAN_CTX_HTTP_TOKEN	Supply a fixed dashboard credential; --auth-token=... takes precedence. Prefer the environment to avoid putting credentials in shell history.
LEAN_CTX_SCRAPE_TOKEN	Read-only credential accepted for GET /metrics, not full dashboard access.
LEAN_CTX_DASHBOARD_OPEN	Default reveal mode: browser, none or vscode; command flags take precedence.
--no-auth / --auth=false	Explicitly disable bearer-token authentication. Browser origin/host checks remain, but they do not authenticate arbitrary network clients.

Keep the default local binding for personal use. A non-loopback bind changes who can reach the dashboard; reverse-proxy or container deployment needs its own access controls and transport protection. The dashboard is not the separate MCP HTTP server.

Troubleshoot the connection

• Port already in use: reuse the existing instance or choose --port=3334. Do not terminate an unrelated process to reclaim the default port.
• Token required / unauthorized: reopen the URL printed by the running instance. A stale browser tab can hold an older credential.
• Wrong project or empty map: specify --project=..., then check index status.
• Nothing opens on a remote/headless machine: use --open=none and an authenticated connection to the appropriate machine.
• Looking for the old terminal UI: lean-ctx watch was removed. Use this dashboard, lean-ctx cep for terminal metrics, or lean-ctx index watch for index updates.

This guide combines the inspected command help from runtime 3.10.2 and the source revision shown below. Token persistence and individual panels can differ between builds; use your installed lean-ctx dashboard --help and the running instance’s URL as the operational reference.

Sources & versions4 references · Reviewed 18 Sept 2026

• mod.rsrust/src/cli/dispatch/network/mod.rsReviewed checkout
• mod.rsrust/src/dashboard/mod.rsReviewed checkout
• cockpit-nav.jsrust/src/dashboard/static/components/cockpit-nav.jsReviewed checkout
• vscode_open.rsrust/src/dashboard/vscode_open.rsReviewed checkout

Core checkout

5198ea1867

Installed runtime

3.10.2

SDK release

1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility