← ClaudeAtlas

dev-looplisted

Builds and runs musterd locally against the real data dir for manual testing. Covers where the dashboard URL and tokens live and how to stop cleanly.
Zalaras/muster · ★ 2 · Web & Frontend · score 71
Install: claude install-skill Zalaras/muster
> **Maintainer note:** Authored at m0-skeleton completion per the plan's Implementation > Notes. Runs in the main session — it > starts a long-lived process the user interacts with. Run the Muster daemon locally for manual testing. ## Build and run ```bash make run ``` This builds `bin/musterd` and the dashboard assets (`internal/webui/assets/`), then runs the daemon against the **real** data dir (`~/Library/Application Support/Muster`) serving those assets from disk (`-web-dist internal/webui/assets` — the dev override, so the edit-TS → `make web-build` → reload loop needs no Go relink), listening on `127.0.0.1:8765`. The startup log line includes `dashboard_url` — that URL (with the UI token baked in) is what to open in the browser. Because `make run` occupies the terminal, launch it in the background (`run_in_background`) or tell Damian to run `! make run` himself if he wants to watch the logs. `make run` now also opens the dashboard in the default browser once it's up (plan tmux-installation REQ-6, default `-open=true`) — a real terminal stdin is required for this to fire, so it does nothing when launched via `run_in_background` (no terminal stdin there). Pass `-open=false` to suppress it either way; the dashboard URL is on the startup log line regardless. ## Where things live - **`~/Library/Application Support/Muster/tokens.json`** (0600, rewritten every startup): `{"dashboardUrl", "uiToken", "ingestToken"}`. Read this if you need the dashboard URL or an inge