Skip to main content
comet dashboard launches a local read-only browser dashboard. One snapshot contains Classic/OpenSpec and Native data, while the workflow switch in the upper-left corner shows only the selected workspace. It is read-only — it never modifies any files, so you can launch it safely at any time.
This page is the command reference for comet dashboard. To learn about the dashboard UI layout, artifact grouping, task donut charts, light/dark themes, and screenshots, see Dashboard overview.

​
Quick start

Run it from the root of a project that contains changes:
By default it starts at http://localhost:4321 and automatically opens the browser. The terminal will show:

​
Command options

When —port is occupied, it automatically searches upward for an available port (up to 50 retries). —port 0 lets the system assign one. The port must be an integer from 0–65535, otherwise an error is raised.

​
Script / CI usage

Print a one-time JSON snapshot without starting the server:
Specify a port and skip auto-open (useful for remote development):

​
What the dashboard shows

The Classic workspace reads the root selected by classic.artifact_layout: docs/openspec/changes/ for the default documentation layout or openspec/changes/ for a retained legacy layout, including the corresponding changes/archive/ directory. The Native workspace reads the configured Native artifact root from .comet/config.yaml. Both are read-only and best effort; a Native collection failure does not prevent the Classic snapshot from being returned. The browser shows one selected workflow at a time, and switching does not change project state. The Changes Explorer loads lightweight change rows in pages and fetches complete detail only after you select a row. Classic and Native keep the current detail visible while another detail request is running and offer a retry when it fails; on a large project, continue scrolling to load the next page.

​
View registered Git worktrees

Dashboard discovers the worktrees registered for the current Git repository and treats each one as an independent change source. The list shows the corresponding branch or worktree label, so a change from another worktree is not attributed to the current directory.
In the Native workspace, independent changes appear as root entries. A Supervisor Change can be expanded to show child status, branches, and progress. Selecting either the Supervisor Change or a child opens its corresponding detail while Dashboard remains read-only.

​
Native changes

The Native workspace provides Active, Archived, and All filters. Its status data comes directly from Native Runtime projections, archive preflight, and the conflict radar:
  • Phase: Shape / Build / Verify / Archive
  • Verification evidence freshness and archive readiness
  • Continuation disposition and whether a user decision is required
  • Structured finding codes
  • Related changes with definite conflicts or possible overlaps
  • Markdown previews for the brief, changed Specs, and verification report
  • Latest checkpoint, next action, and progress timestamps
  • Capability scope, Acceptance coverage, and implementation-scope summaries
  • Repair status and project Git summary
The Native workspace projects only bounded checkpoint and evidence summaries; it does not expose hashes, Runtime paths, raw evidence, or other internal state files, and it offers no progression, repair, or archive controls. Use the comet native commands for complete detail and all writes. With --json, the same snapshot includes a native field with schema comet.dashboard.native.v1 when Native is available. The field is omitted when the project does not enable Native.

​
Classic changes

Starting in 0.4.0-beta.4:
  • The change workspace remains inside the viewport while the left explorer is visible.
  • Opening and closing an artifact preview preserves the previous scroll position.
  • Archived changes show a completed state instead of recommending verify again.
  • Archived Design Docs, Plans, and verification reports resolve from project-root docs/superpowers/ paths and remain previewable.

​
Project-level information

  • Project name, path, and generation time
  • Summary: number of active changes, archived count, verify failures, incomplete tasks, and dirty file count
  • Git snapshot: branch, HEAD, dirty file list, and recent commits

​
Per change

  • Name, status (active/archived), path, and update time
  • Workflow and phases (open/design/build/verify/archive) — shown as a lifecycle step bar
  • Task completion (completed/total, incomplete items, per-section) — shown as a donut chart
  • Artifacts grouped by source (OpenSpec / Superpowers / Comet), with presence status shown within each group (generated/not generated/not required)
  • Artifact presence (proposal, design, tasks, plan, verifyReport, cometYaml) + content preview (max 256 KiB, with file size and update time metadata)
  • Verify result (pending/pass/fail/unknown) and summary
  • Next step (active changes only): recommended slash commands and the reasoning
  • Risk items (info/warning/error levels + recovery suggestions)

​
Risk codes

​
Auto-refresh and theme

The front end auto-refreshes every 30 seconds. There is also a manual refresh button, a search box, and tabs (active/archived/all). The artifact drawer includes a lightweight Markdown renderer. The top-right toolbar has a light/dark theme toggle: on first visit it follows the system preference (prefers-color-scheme); once you manually switch, the choice is persisted to localStorage. See Dashboard overview · Theme toggle.

​
Demo mode

Append ?demo to the URL to load demo data (without reading real changes), handy for previewing the UI:

​
Security

  • The server binds only to 127.0.0.1 (localhost) and is not exposed externally.
  • Static file serving has path traversal protection.
  • Artifact previews have a size limit (256 KiB; larger ones are marked truncated).
  • The artifact drawer remembers the page scroll position and restores it when closed.

​
Next steps

Last modified on August 13, 2026