Developer Uses Claude Code to Build USB Dongle That Auto-Plays Chrome Dino Game
Hardware and Firmware Details
A developer created a USB dongle that automatically plays Chrome's offline Dino game without requiring host-side software or browser extensions. The device uses an ATtiny85 (Digispark) microcontroller with 8KB flash and 512 bytes of RAM, costing approximately $2.
How It Works
The dongle plugs into any PC and appears as a standard USB HID keyboard. It uses two LDR (light-dependent resistor) sensors mounted on the monitor to detect obstacles in the game:
- Lower sensor detects cacti
- Upper sensor detects birds
When obstacles are detected, the device sends appropriate keyboard commands (jump or duck) to control the game character.
Claude Code's Role in Development
The developer used Claude Code as the primary development partner for the firmware, which is written in bare-metal C using avr-gcc (not Arduino). Specific contributions included:
- Writing the V-USB HID keyboard stack integration and report descriptor
- Designing dual-sensor obstacle classification logic through iterative development
- Creating pulse-width envelope measurement for speed-adaptive timing
- Handling the fork-shaped cactus sprite issue (multiple sub-pulses merged via gap threshold)
- Writing the full README, PLAN.md, and Makefile
Technical Implementation
The adaptive timing system addresses the game's acceleration by measuring how long each obstacle takes to pass the sensor, using a rolling minimum filter, and scaling the jump delay accordingly. Codex performed a code review that caught a bug in the envelope tracking logic where sensor polarity was inverted in four places.
The total firmware size is 2699 bytes. Hardware assembly, sensor mounting, LM393 potentiometer calibration, and physical testing were done manually by the developer.
Key Differentiators
- USB HID keyboard implementation requires no host-side Python or browser extensions
- No servo or solenoid pressing the spacebar
- Dual vertically-stacked sensors for obstacle differentiation
- Adaptive timing that remains accurate as game speed increases
📖 Read the full source: r/ClaudeAI
👀 See Also
Claude Code's /insight command analyzes developer workflow patterns from real usage data
A developer building a personal finance iOS app used Claude Code's new /insight command to analyze 22 days of usage: 529 messages, 47,604 lines of code, 632 files touched, and 146 commits. The report identified effective patterns like an 'audit-then-batch-fix pipeline' and flagged time-wasters like debugging loops.
Practical Limits of Multi-GPU AI Workstations: Lessons from a 9× RTX 3090 Build
A developer shares experience running 9 RTX 3090 GPUs for AI work, finding diminishing returns beyond 6 GPUs and recommending Proxmox for LLM experimentation. The RTX 3090 remains compelling at $750 for 24GB VRAM.
Reducing AI Agent Context Bloat with Single Workspace Architecture
A developer shares how they reduced AI assistant startup context from 27,000 to 4,000 tokens by implementing a single workspace approach instead of complex agent swarms, using channel-level identity injection and segregated memory folders.
Dynamic Workflows in Claude Code: 3x Feature Velocity with Parallel Subagents
Parallel subagents in Claude Code cut feature build time from 4-6 hours to 1.5-2 hours. One developer shares their workflow: 3 agents work simultaneously on API docs, tests, and code.