CLI-agnostic read-only web dashboard. Point it at any CLI that can list\nresources as JSON and it derives the dashboard at runtime: one tab per\nresource, a generic table over whatever columns the rows have. New resource →\nnew tab; new column → new table column; zero code changes.
\nIt ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, messaging\ngroups, wirings, users, roles, …) plus docker, but the same config shape\nworks for any list-as-JSON CLI.
node:sqlite),\nno build step,\nvanilla-JS frontend.execFile the configured\nargv templates; {resource} is the sole substitution and is validated\nagainst the discovered/static resource allowlist. Never a shell.views/ncl-overview.js view plugin.cp clidash.config.example.json clidash.config.json # then edit paths if needed\nnode server.js # uses ./clidash.config.json\nCLIDASH_CONFIG=/path/to.json node server.js\nPORT=4690 BIND=127.0.0.1 node server.js # env overrides\nRun it from tools/clidash/; the example config uses paths relative to the\nNanoClaw root two levels up, so it works out of the box once ncl is built.
clidash.config.json){\n \"port\": 4690,\n \"bind\": \"127.0.0.1\", // never a public interface; a tailnet IP at most\n \"refreshSeconds\": 60,\n \"clis\": {\n \"ncl\": {\n \"bin\": \"bin/ncl\", // relative to cwd below\n \"cwd\": \"../..\", // the NanoClaw root\n \"discover\": { \"args\": [\"help\"], \"parser\": \"ncl-help\" }, // runtime resource discovery\n \"list\": [\"{resource}\", \"list\", \"--json\"], // argv template\n \"output\": \"json\", // or \"jsonlines\" (docker/kubectl style)\n \"unwrap\": \"data\" // dot-path into a response envelope\n },\n \"docker\": {\n \"bin\": \"docker\",\n \"resources\": [\"ps\", \"images\"], // static alternative to discover\n \"list\": [\"{resource}\", \"--format\", \"{{json .}}\"],\n \"output\": \"jsonlines\"\n }\n }\n}\n{resource} may appear as a whole argv element or inside one — e.g. a remote\nCLI via ssh: \"list\": [\"-i\", \"key.pem\", \"user@host\", \"ncl {resource} list --json\"].
Per-CLI env (merged over the server's env) and cwd are supported. See\nclidash.config.example.json for the full NanoClaw config, including the\nenrich/badges/summary table decorations and the activity/logs/docs\nsections.
| Route | \nReturns | \n
|---|---|
GET /api/clis | \nconfigured CLIs + discovered/static resources (discovery cached 60s) | \n
GET /api/r/<cli>/<resource> | \n{ok, rows, fetchedAt} — coalesced, 10s exec timeout | \n
GET /api/view/<cli>/<view> | \ncurated view plugin from views/<cli>-<view>.js | \n
View plugins are the only per-CLI code, and optional: a default-exported\nasync function receiving { fetch } (bound to that CLI) returning JSON.\nviews/ncl-overview.js joins groups + sessions + messaging-groups + wirings\ninto per-agent status cards (green <15m / amber <2h / red older).
npm test # unit + integration (node:test, stub CLI — no real CLI needed)\n./test/smoke.sh # against a running instance\nclidash binds 127.0.0.1 by default. To reach it from other devices, bind a\nprivate (e.g. tailnet) IP — never a public interface; the network is the\nauth boundary. Example systemd user service:
# ~/.config/systemd/user/clidash.service\n[Unit]\nDescription=clidash read-only CLI dashboard\n\n[Service]\nWorkingDirectory=%h/nanoclaw/tools/clidash\nExecStart=/usr/bin/node %h/nanoclaw/tools/clidash/server.js\nEnvironment=BIND=127.0.0.1\nRestart=on-failure\n\n[Install]\nWantedBy=default.target\nThen systemctl --user enable --now clidash.