claude-code-buddy

Claude Code Buddy Skill

Connect to a device on the local network and push Claude Code events to it. After connecting, the Stop and Notification hooks fire automatically — this skill covers the on-demand actions (connect, notify, usage) and the plain-language config tuning.

The plugin only speaks the HTTP contract below. The device decides the actual LED / display / voice feedback; the plugin never draws anything itself.

Config

Path: ~/.config/claude-code-buddy.json (file permission 0600).

{
  "devices": [
    { "label": "My Device", "host": "lamp-a1b2.local", "last_known_ip": "192.168.1.50", "password": "the-web-admin-password" }
  ],
  "default_host": "lamp-a1b2.local",
  "usage_threshold": 80,
  "sounds_enabled": true,
  "task_done_enabled": true,
  "notify_enabled": true
}

• host is the device's mDNS hostname (like lamp-a1b2.local); last_known_ip is the cached address used to avoid re-resolving every time.
• password is the device's admin password — the same one used to log into the device's web UI. The daemon gates its LAN endpoints (notify / usage / approval) with it, sent as an Authorization: Bearer header; without it those calls return HTTP 401. Discovery (/health) stays open, so the device is still findable before a password is set. Stored only in this 0600 file.
• Shared helpers live in scripts/buddy_client.py (config load/save, discovery, send(), usage fetch). Prefer them over re-implementing.

---

1. Discover / Connect

Find the device on the LAN and save it to config.

When to use: "connect my device", "set up my device", or when a POST fails with a connection error/timeout (the cached IP is stale).

Run discovery

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/discover.py

How it works (automatic): cache check (cached IP → /health) → mDNS browse for _autonomous._tcp → /24 subnet /health sweep. Returns the found device(s) as JSON, e.g.:

[{ "host": "lamp-a1b2.local", "ip": "192.168.1.50" }]