Tidbyt Status Display

Provides an HTTP API exposing OpenClaw agent status as JSON for displaying on Tidbyt 64x32 LED devices with activity, emoji, and task details.

This package appears to do what it says: run a small local HTTP server that inspects ~/.openclaw/agents/main/sessions/*.jsonl metadata and serves a JSON /status endpoint for a Tidbyt app. Before installing, note: 1) The Tidbyt Starlark file (scout_status.star) and a packaged .skill file are referenced in the docs but are not included — you will need that .star app to render/push to your Tidbyt. 2) The server returns CORS: '*' and the docs show opening TCP port 8765; if you expose this port to a wider network or the internet, your agent's status (and timestamps/filenames) will be publicly accessible — consider restricting access (firewall rules, local-only binding, VPN, or add authentication/TLS) if privacy matters. 3) The code only uses file metadata (modification times and filenames) and does not read session file contents, but you should review ~/.openclaw/agents/main/sessions/ yourself to confirm it contains only metadata you are comfortable exposing. 4) Installing the systemd service requires sudo and will run the server as your user; verify the ExecStart path and the service file before enabling. If you want the extra assurance, ask the author to include the missing scout_status.star file and the packaged skill, and consider adding optional basic auth or IP-restriction to the status endpoint.

Type: OpenClaw Skill Name: tidbyt-status Version: 1.0.0 The OpenClaw skill 'tidbyt-status' is designed to expose the agent's status via a local HTTP API for Tidbyt LED displays. The `scripts/status_server.py` file correctly implements this by reading agent session files (`~/.openclaw/agents/main/sessions/*.jsonl`) and serving status JSON on a local port (default 8765). The `install.sh` script and `SKILL.md` provide clear, user-facing instructions for setup, including options for background execution and systemd service creation, which requires explicit user `sudo` commands. There is no evidence of prompt injection against the agent, data exfiltration, unauthorized remote access, or any other malicious intent. All observed behaviors align with the stated purpose of providing an agent status display.