OpenClaw Studio

Use when the user wants a local visual operations dashboard for OpenClaw, with a cute robot presentation, live status visibility, chat access, efficiency tre...

Before installing or running these scripts: (1) Do not run install_launchd.sh until you have inspected the runtime Python files (server.py, autoheal.py, app_watchdog.py). They are referenced by the launchd plists but are missing from the provided bundle — installing services that point to missing or unknown executables is risky. (2) If you find those Python files elsewhere, review them for network activity, credential handling, and what the auto-heal/watchdog actually do (restarts, external calls, file writes). (3) Expect the install scripts to create persistent per-user LaunchAgents that auto-start processes and write logs under the repo directory — only proceed if you trust the code. (4) The package appears macOS-specific; don’t attempt the launchd install on other OSes. (5) If you want to try the dashboard without persistence, run ./run_monitor.sh in a terminal first and confirm server.py behaviour and any network connections, then consider background/launchd install. If you cannot review the missing Python files, treat this package as untrusted.

Type: OpenClaw Skill Name: openclaw-studio Version: 1.0.1 The bundle includes `install_launchd.sh`, which establishes persistence on macOS by installing three background services (`monitor`, `autoheal`, and `watchdog`). This is a high-risk capability that allows code to run automatically on system startup. Additionally, there is a discrepancy as `autoheal.py` and `app_watchdog.py` are configured for persistence but are omitted from the 'Core files' list in `SKILL.md`. While these features align with the stated goal of a monitoring dashboard, the use of persistence for undocumented scripts is a significant security risk.