It’s a work in progress, but, yes, you can run Claude Code through a Furby.
Hardware:
• Stock Furby Connect (2016). No mods, just BLE
• Mac
• USB mic for voice capture
BLE (Bleak):
• Connects via GATT characteristic to Furby's GeneralPlus chip
• Two command types: antenna LED color [0x14, R, G, B] and stock actions (eyes + motors + sound) [0x13, ...]
• Write-only
• Auto-reconnect on drop
Voice (sounddevice + Whisper):
• 16kHz mono stream, RMS energy detection
• Starts recording at 0.3s above threshold, stops after 1.5s silence
• Clips sent to Whisper API → checked for wake phrase ("hey furby")
• Wake word only → records a second clip for the actual command
Claude Code (subprocess):
• Spawns claude -p "<command>" with stream-json output
• --dangerously-skip-permissions (no terminal to confirm)
• Whitelisted tools: Read, Write, Edit, Bash, Grep, Glob
Resumes session for conversation context
• Parses stdout line by line → system, assistant, result events
Furby reactions:
• Every Claude event maps to a stock Furby action + antenna color
• Thinking → giggle + purple
• Writing files → hollywood lights + green
• Bash → ninja dream + yellow
• Success → stars + gold
• Error → eyes squeezed + red
• + 12 more
Working on custom DLC eyes now:
• 64x64 pixel art uploaded to Furby's flash over BLE at ~4KB/s
• Terminal prompt, magnifying glass, loading spinner, checkmark, X mark
• 6-bit palette-indexed, packed 4px per 3 bytes
I have a massive Furby-induced headache. Do not recommend trying this at home.
I’m currently deciding how to use Claude, not which model.
App: easiest, but I keep burning tokens + attention bouncing between Chat/Cowork/Projects.
CLI: lean + more control, but it’s annoying if you’re not already a terminal person.
Right now I’m using both + testing Obsidian