LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

Softwareterminalcoding-agentsopen-source

This Terminal Snake Game Freezes When Your Coding Agent Needs You

A tiny local signal file connects the diversion to Claude Code and Codex, with a separate alert for permission requests.

Chris Pirillo plays Snake on a tiny handheld while a small robot rings a bell beside him and the snake on the screen freezes.
Illustration: LockerGnome

Your coding agent finishes. The snake stops moving before you have to choose between answering it and crashing into a wall. Somebody finally gave the loading-screen diversion an exit strategy.

The maker’s README describes a small signal file between the agent and the game. Claude Code or Codex invokes a notification command; the arcade polls the file several times a second. Completion and requests for input produce different banners.

“It pauses on the banner,” the README says. That matters more than a notification badge buried under another window. The entertainment yields to the thing it was supposed to help you wait for.

The README also documents a sponsor-message download, which can be disabled. Free software still deserves a look at what it fetches.

Kuldeep Mahour’s account of building it describes a notification bug that would be especially annoying in a game: the first implementation could be late precisely because you were playing. Claude Code’s general notification for a permission prompt waits for about six seconds without typing, he explains. Snake involves a fair amount of typing if you intend to keep the snake alive.

The fix listens directly for the permission-request event. That fires when the prompt appears, rather than waiting for an idle interval. Crucially, the hook doesn’t grant permission. The interruption still needs your answer. A doorbell can tell you someone is outside without opening the door for them.

Mahour writes that using the file’s timestamp lets consecutive completion events register separately. Rewriting the same word still changes the timestamp; the next finished turn gets its own interruption. The watcher also starts with the existing timestamp, so an old signal doesn’t ambush a newly opened game. Those details make the difference between a useful timer and the microwave that keeps reminding you about yesterday’s coffee.

The README gives the return trip some care, too. Losing focus pauses play, and a three-second countdown precedes resuming. At a banner, q leaves and c continues. The player can ignore the interruption deliberately, rather than discovering ten minutes later that a finished task has been waiting in another tab.

Setup also reaches outside the game: it adds agent integration, backs up the affected configuration files and offers an uninstall command. Existing agent sessions need a restart to pick up those hooks. That makes a manual notification test worthwhile before relying on a banner during actual work.

Completion alerts can become part of the tool people are already looking at, provided the notification remains separate from approval. The game demonstrates that distinction without pretending a beep verifies the work. Someone still has to return to the agent, inspect the changes and decide whether the next action makes sense. How well does that handoff hold up when several agents finish at once?

More Software

Every Software story →