jackboxlisted

# Jackbox autopilot Plays Jackbox party games as a player by driving **jackbox.tv** (the phone-controller site) in a real Chrome window over CDP (Chrome DevTools Protocol). The autopilots run locally in tight loops and use the Claude API for humor/judgment, so they keep up with fast game timers and never steal the user's screen focus. Plays as **AlexsClaude** by default (<=12 chars; signals to friends it's Alex's bot). ## Architecture (why it's built this way) - **One persistent Chrome, many short node calls.** `launch.sh` starts Chrome with `--remote-debugging-port=9222` on a **throwaway profile** (`/tmp/jackbox-chrome-profile`) so the user's real Chrome is never touched. Every script then `connectOverCDP('http://localhost:9222')`, acts, and disconnects with `browser.close()` -- which **detaches CDP but leaves Chrome running**. This keeps the game session alive across separate tool calls. - **Autopilots are local loops, not turn-by-turn.** A turn-based agent (screenshot → think → click) is too slow for Quiplash voting windows and Tee K.O. phases. The autopilots (`quiplash.js`, `teeko.js`) poll the DOM every 0.6-1s, detect the phase, and act in-process. Launch them with `nohup … & disown` so they survive. - **The Claude API does the creative/judgment work**, not the loop. Opus 4.8 writes answers/slogans/draws; Haiku judges text votes fast; Sonnet does vision votes. ## Setup / prerequisites - Google Chrome installed at `/Applications/Google Chrome.app`. - Playwright avai