Keyboard-only play for a Godot roguelike, and Claude now playtests it
Making Vestiges playable without a mouse took nearly two days of part-time work, with Claude busy throughout. Then they set up an MCP server so Claude can play the game like a player would.
Done withClaudeSpotted· by HN user ksaun· Oct 16, 2026
Result Nearly two days of part-time work
“I added full support for keyboard-only play (which was a more substantial effort than I'd anticipated, taking close to two days (very part-time for me, but Claude was fairly busy))”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
For their narrative strategy rogue-like game Vestiges, they added full support for keyboard-only play, working with Claude on the implementation. They also set up an MCP server so that Claude can playtest the game as a player would.
How it went
Keyboard-only support was a more substantial effort than they had anticipated, taking close to two days of their own part-time work, during which Claude was fairly busy. They had only just started making use of the new MCP playtesting setup.
Try it yourself with Claude
Pick an accessibility or input-method gap in a game or app you're building, such as full keyboard-only support. Work through it with an AI coding agent, implementing and testing each input path as you go. Once it's done, consider setting up an MCP server or similar interface so the same agent can play through or exercise the feature itself.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.
Working on a Quake project, Claude decided on its own to build a test suite: demo playbacks with snapshots compared pixel by pixel, plus recorded demos whose screenshots it checked for each element.
After building a minimal proof assistant, the writer asked Claude how they knew the prover was actually sound. Claude checked, found five different ways it could prove false theorems, and fixed them.
Four years after shelving a homemade RSS reader and selling off its $500 domain, the writer built it this year with Codex and Claude. They use it daily, along with 30 other strangers who found it public.
Chasing a childhood itch for the exact 1996 After Dark Flying Toasters screensaver, the writer turned to Claude. It did a lot of good reverse-engineering work, but kept inventing details that needed pushback.