The hardest part of AI-assisted coding isn't the code. It's the waiting.
You know the moment. You fire off a prompt. Claude Code starts thinking. And you enter the dead zone - too short to context-switch to another task, too long to just stare at a blinking cursor.
You check your phone. You refill your coffee. You open Twitter. You close Twitter. You open it again. Meanwhile, Claude finishes and you don't notice for three minutes.
I built a T-Rex runner game that lives inside your tmux session. Press ctrl+b and release and then press g, and a pixel-art dinosaur game takes over your terminal. Jump over cacti, dodge birds, watch the day turn to night.
When Claude Code finishes its task, a notification pulses across the game screen. Press Q to quit and get back to work. No alt-tabbing. No missed completions.
One curl command. Zero extra dependencies (beyond Python 3 and tmux).
dinobot
Prerequisites:
brew install it if missing)One command:
curl -fsSL https://raw.githubusercontent.com/CRACK-BREAK-MAKE/dinobot/main/install-dino.sh | bashThat's it. The installer:
~/.claude/games/ and drops the game therectrl+b release and press g) to your ~/.tmux.conf~/.claude/settings.json so the game knows when Claude is doneIf you prefer to inspect before running:
git clone https://github.com/CRACK-BREAK-MAKE/dinobot.git
cd dinobot
cat install-dino.sh # read it first
bash install-dino.shStart any tmux session (or use the one Claude Code already runs in), then:
Key Action
Ctrl+b then g | Launch the game |
SPACE or UP | Jump |
DOWN | Duck |
P | Pause |
Q | Quit and return to Claude |
The game runs as a tmux popup overlay - it doesn't touch your main terminal session. Your Claude Code session keeps running underneath.
This is not your average terminal game. The renderer uses Python's curses library with half-block pixel rendering for smooth visuals:
~/.claude/games/.highscoreAll of this in a single Python file. No dependencies beyond the standard library.
This is the part that makes it actually useful instead of just fun.
The installer adds two hooks to your Claude Code settings (~/.claude/settings.json) :
Both hooks do the same thing: create a signal file at ~/.claude/games/.claude_done.
The game checks for this file every frame. When it appears, a persistent alert pulses across the screen:
+---------------------------------+
| |
| Claude has finished! |
| Press q to return |
| |
+---------------------------------+Press q, the game exits, the tmux popup closes, and you're right back where you left off. The signal file gets cleaned up automatically.
No polling. No browser tab. No notification you accidentally dismissed. Just a dinosaur telling you Claude is done.
Changed your mind? Clean removal:
rm -rf ~/.claude/games~/.tmux.conf ( the one with dino.py )~/.claude/settings.jsonIs it necessary? No.
Does it make the wait enjoyable? Very much yes.
Will it improve your sprint velocity? Let's not ask that question.
Sometimes the best developer tools are the ones that make you smile while you wait for the real work to finish.
GitHub: CRACK-BREAK-MAKE/dinobot
Your turn: I built a dinosaur game. What's the craziest thing you'd build while waiting for Claude Code to finish? Drop it in the comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 25 | |
| 19 | |
| 18 | |
| 14 | |
| 13 | |
| 11 | |
| 10 | |
| 9 | |
| 6 | |
| 4 |