Live Dashboard - AI Blueprint Docs

Open a read-only local dashboard for the Blueprint roadmap, current work, completed history, findings, Git state, and next action.

The Blueprint CLI can open a live browser view of the project without starting the application or changing any files.

Open the dashboard

With the optional global CLI installed, run this from a Blueprint project or any nested directory:

blueprint dashboard

Without the global CLI, run the same dashboard through npx:

npx create-ai-blueprint@latest dashboard

The command opens the dashboard in your browser and keeps the terminal process running. Press Ctrl+C when you are finished.

Interactive installs and updates offer the matching global CLI for the shorter command, but it is not required. The older ui command remains as a deprecated alias.

Use --target when you are outside the project:

blueprint dashboard --target /path/to/project

Use --no-open when you want the local URL without opening a browser automatically:

blueprint dashboard --no-open

What it shows

The dashboard refreshes immediately when Blueprint files or Git state change, with a slower fallback refresh if a file event is missed. It shows:

Project configuration state and regular and Continuous quality-gate modes
The complete build-plan roadmap with done, current, next, and planned work
The active feature, fix, or rollback and its build-step checklist
Completed features, fixes, and rollbacks from Blueprint history
Active findings and completion blockers
The current branch, changed-file count, and upstream state
One deterministic next command and the reason for it

AI Blueprint dashboard showing PortDoc at feature 18 with a reviewed implementation run active, three of five steps complete, and 24 of 25 build-plan items complete. — PortDoc during a normal implementation run, with current activity, feature progress, project state, and the roadmap visible together.

Local-only boundary

The dashboard binds to 127.0.0.1 on an available port. It is available only on the local machine while the CLI process is running. It does not start the project’s development server, execute workflow commands, edit files, store project state, send telemetry, or make external requests.

The browser listens for local file-change events while the tab is visible and keeps a slower polling fallback. Each response is rebuilt from the current Blueprint files and Git state, so running commands, checked steps, findings, branch changes, and archived work appear without restarting the dashboard.

See CLI Status for the terminal report built from the same project state.