Live Sessions Dashboard

Live dashboard viewer for OpenClaw sessions (CLI + web) that shows color-coded states, token/cost totals, and shareable HTML panels. Requires local OpenClaw...

This skill appears to do what it says: it queries your local OpenClaw CLI to produce a live terminal and HTML dashboard. Before installing or running it: - Verify the `openclaw` binary on PATH is the expected official CLI (subprocess calls execute that binary). Run the scripts on a host that is allowed to read your gateway. - Be cautious with the log subscription: tailing `openclaw logs --follow` can surface prompts, tool args, or secrets (the code only extracts sessionId and does not persist raw log messages, but logs may still appear in process memory). If you are unsure, run with the `--no-subscribe` flag or run on a host without log access. Note: the SKILL.md suggests an AGENT_MONITOR_NO_SUBSCRIBE env var, but the scripts do not actually read that variable — you must pass `--no-subscribe` on the CLI. - If you publish the generated HTML to a remote or public location, be aware it contains internal session identifiers, counts, token/cost estimates, model names, and timestamps; treat it as internal information. - The package has no homepage and unknown owner; if you need strong assurance, review the full scripts locally (they are included) and test in a non-production environment. If you want a cleaner bill-of-materials from the author, ask them to: (1) either implement respect for AGENT_MONITOR_NO_SUBSCRIBE or remove that doc line, (2) document the exact behavior when `openclaw` errors, and (3) sign or publish a homepage/source repo so you can confirm provenance.

Type: OpenClaw Skill Name: sessions-dashboard Version: 1.0.1 The skill is classified as suspicious due to its default behavior of subscribing to `openclaw logs --json --follow` via `scripts/agents_cli_monitor.py`. The `SKILL.md` explicitly warns that these logs "can contain prompts, tool arguments, secrets, or PII." While the code does not appear to exfiltrate or persistently store this sensitive log content (it only extracts session IDs and update times), the default access and processing of such a sensitive data stream, even for a stated purpose, represents a risky capability without clear malicious intent. Users are warned and can opt-out with `--no-subscribe`, but the default behavior warrants caution.