add-dashboard

Installs a monitoring dashboard that pushes NanoClaw state snapshots and logs over HTTP.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-dashboard-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-dashboard
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/add-dashboard
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill add-dashboard-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @nanoco/nanoclaw-dashboard, better-sqlite3, vitest, typescript.

What problem does it solve? NanoClaw runs agents in containers with no built-in visibility into sessions, channels, token usage, or logs. This Skill adds a local monitoring dashboard so operators can observe agent groups, message activity, and context window usage in real time. ## Core Features & Use Cases - Dashboard Installation: Installs the @nanoco/nanoclaw-dashboard npm package and copies a pusher module that POSTs JSON snapshots every 60 seconds and tails the log file every 2 seconds. - Verified Integration: Ships behavior and AST-based wiring tests that confirm the pusher is correctly imported and awaited in src/index.ts after DB init and before the boot-complete log. - Use Case: After deploying NanoClaw with Telegram and WhatsApp channels, run this Skill to get a browser dashboard at localhost:3100 showing live channel status, per-session messages, token consumption by model, and streaming logs. ## Quick Start Ask the agent to add the monitoring dashboard to your NanoClaw installation and configure the DASHBOARD_SECRET and DASHBOARD_PORT environment variables.

Frequently Asked Questions about add-dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a monitoring dashboard to NanoClaw?

Install @nanoco/nanoclaw-dashboard via pnpm, copy the dashboard-pusher module into src/, wire an awaited startDashboard() call into main() in src/index.ts, and set DASHBOARD_SECRET and DASHBOARD_PORT in .env. Then build, run the shipped vitest tests, and restart the service.

What metrics does the NanoClaw dashboard show?

The dashboard shows agent groups, sessions with container state, channel live/offline status, per-session inbound and outbound messages, user privilege hierarchy, token usage by model and group, context window usage, 24-hour activity buckets, and real-time streamed logs.

Why does the NanoClaw dashboard show no data?

The pusher sends its first snapshot 60 seconds after startup, so wait one interval before checking. If it stays empty, check the service logs for push errors and confirm DASHBOARD_SECRET is set, since startDashboard no-ops without it.

Why do I get 401 errors from the dashboard API?

A 401 means the Authorization bearer token does not match. Verify the DASHBOARD_SECRET value in your .env matches the secret used in the request header, then restart the service so the pusher picks up the updated value.

How do I remove the dashboard from NanoClaw?

Delete the dashboard-pusher source and test files from src/, uninstall @nanoco/nanoclaw-dashboard, remove the dashboard block from main() in src/index.ts, delete DASHBOARD_SECRET and DASHBOARD_PORT from .env, and rebuild. The removal is safe to re-run.