Command Center is a local-first planning cockpit for code repositories.
It pulls planning state you already maintain (GSD/GSD2 docs, Holistic context, roadmap artifacts), normalizes it, and helps you answer:
- Where is this repo in the workflow loop?
- What is blocked right now?
- What should happen next?
- How does this compare across repos?
Milestone status (current):
- ✅ M001 complete — import-first foundation
- ✅ M002 complete — resume-first cockpit intelligence + trust surfaces
- ✅ M007 complete — launcher hardening + cockpit actionability iteration
- ▶ M008 active (planned) — premium UX redesign + onboarding clarity
For planning detail, see ROADMAP.md.
The launcher lifecycle is verified in this environment:
npm run cc:doctor✅npm run cc:launch -- -NoBrowser✅npm run cc:stop✅
Launcher diagnostics and stop now use resilient port probing to avoid earlier PowerShell networking-call hangs in this setup.
- Workspace project discovery
- Source artifact detection
- Canonical SQLite planning model
- Plan snapshot API
- Imports for:
.gsd/PROJECT.md.gsd/REQUIREMENTS.md.gsd/DECISIONS.md
- Import provenance + warning tracking
- Workflow State panel (confidence + evidence)
- Workflow Readiness panel (stack/component gaps)
- Continuity panel (freshness + checkpoint hygiene)
- Next Action panel (blocker-aware recommendation)
- Open Loops panel (next, blocked, unresolved, deferred)
- Explicit interpreted/provenance labels on trust-sensitive surfaces
- One-click desktop Launch shortcut
- One-click desktop Stop shortcut
- Launcher diagnostics command (
cc:doctor) - Troubleshooting matrix + logs
- Footer version is package-driven from
package.json(Command Center vX.Y.Z)
- Node.js 20+ (tested with Node 24)
- npm
- Windows PowerShell (for launcher scripts)
git clone https://github.com/lweiss01/command-center.git
cd command-center
npm installIf you are using your own fork, replace the clone URL with your fork URL.
npm run cc:shortcutCreates/updates:
Command Center.lnk(Launch)Command Center (Stop).lnk(Stop)
npm run cc:doctorYou’ll get PASS/WARN/FAIL checks for host tooling, ports, shortcuts, and logs.
Desktop:
- Double-click Command Center
Terminal:
npm run cc:launch- Frontend:
http://localhost:5173(launcher uses strict port 5173) - Backend API:
http://localhost:3001/api/projects
Desktop:
- Double-click Command Center (Stop)
Terminal:
npm run cc:stop- Launch (
cc:launchor desktop shortcut) - Select a project card
- Read panels in this order:
- Workflow Readiness
- Continuity
- Workflow State
- Next Action
- Open Loops
- Run the suggested command in Next Action when blocked
- Stop services when done (
cc:stop)
| Command | What it does |
|---|---|
npm run cc:shortcut |
Create/update Launch + Stop desktop shortcuts |
npm run cc:doctor |
Run launcher preflight diagnostics |
npm run cc:launch |
Start backend + frontend and open browser |
npm run cc:launch -- -NoBrowser |
Start backend + frontend without opening browser |
npm run cc:stop |
Stop backend/frontend listeners on ports 3001/5173 |
npm run dev |
Start Vite frontend only |
node server.js |
Start backend only |
npm run build |
Type-check + production build |
| Symptom | Command to run | Where to inspect |
|---|---|---|
| Launch shortcut does nothing | npm run cc:shortcut |
Desktop shortcuts (Command Center*.lnk) |
| Launch hangs/fails readiness | npm run cc:doctor then npm run cc:launch -- -NoBrowser |
.logs/command-center-backend.log, .logs/command-center-frontend.log |
| Ports already in use | npm run cc:stop |
Re-run npm run cc:doctor |
| Need a clean reset | npm run cc:stop then npm run cc:launch -- -NoBrowser |
Launcher console + .logs/* |
For full walkthroughs and panel-by-panel guidance, see docs/USER-GUIDE.md.
- React 19
- TypeScript
- Vite
- Express
- better-sqlite3
- Tailwind CSS
This repo keeps planning + continuity artifacts close to the code:
- ROADMAP.md
- HOLISTIC.md
- AGENTS.md
.holistic/continuity artifacts.gsd/milestone/slice/task planning and summaries