On Sunday afternoon, r/ClaudeAI got a look at what happens when you stop asking Claude Code to write code and start asking it to play games instead. A video posted by u/Wonderful-Ad-8579 shows Claude driving to a waypoint in GTA IV, flying a helicopter in GTA V, and making story choices in Detroit: Become Human — all while the games run in the background and the user’s mouse stays free. Within two hours the post had passed 140 upvotes and 50 comments, and the top of the thread was not an argument about whether it works. It was a joke: Claude is playing GTA V before GTA VI exists.

The tool behind the video is LLM Game Automation MCP, an open-source project on GitHub under the MIT licence. It is not a script that plays one game. It is a general way to let any MCP client — Claude Code is the one in the demo — look at a Windows game and act on it, without the game ever needing to be in front.

What the video actually shows#

The clip is a montage across games rather than a single playthrough: GTA IV driving to a waypoint, a GTA V helicopter, story choices in Detroit: Become Human, plus Totally Accurate Battle Simulator, Halo Wars 2, Phantom Rose and Cities: Skylines. The point of the reel is range, not one run — the same setup driving very different kinds of games.

The one completion claim in the post is specific, and modest in the way that makes it believable: the creator says Claude beat at least one game start to finish, Phantom Rose. Nobody in the thread credibly disputes the footage, and the top comments read as genuine enthusiasm — a moderator summary calling it awesome and impressive, and a long debate about what the tool is actually for, which is where the interesting part starts.

A sports car driving through a neon-lit city street at night, seen from a chase camera, in the style of an open-world driving game
An editorial illustration of open-world night driving, the kind of scene the demo shows Claude navigating. AI-generated illustration.

How it works — and why background play is the point#

Most “AI plays games” setups drive the real desktop: SendInput for the keys, a screenshot of the whole screen for the eyes. That means the game has to stay in front, it steals your mouse and keyboard, and you get exactly one game at a time. This project works per process instead. A DLL called vinput is injected into one game process, and a small CLI talks to it over a per-process named pipe. Input is delivered inside that process on every channel games actually read — window messages, raw input, DirectInput, XInput gamepad — and frames are captured from the game’s own swapchain, not from a desktop screenshot.

Three things follow from that design, and they are the whole pitch. The game never needs focus: vinput fakes focus inside the game and swallows its deactivation messages, so the game keeps rendering in the background. You keep your PC: vinput never generates OS-level input, so your real keyboard and mouse are hidden from a game that is not really in front, and its cursor moves on a virtual cursor instead of yours. And several games can run at once, each with its own pipe and command queue, so several agents can drive several games in parallel.

The MCP server wraps the CLI as 108 tools — launch, capture, click_text, key, pad, key_sequence, move_until_stuck, turn, click_many, nav_go, scene, aim_shoot and more — so any MCP client can look at a game and act on it. Navigation runs off profiles, one JSON file per game for the closed-loop walk, drive and ride tools; version 0.4.8 ships 15 of them, and a new game needs a profile, not new code. Installation is a prebuilt zip and a single claude mcp add command, with Node.js 20 or newer. The project itself is not a weekend sketch: the repository was created on November 2 and already carries 78 commits and 22 releases.

The limits, stated by the builder#

What makes the post land is that the creator does not oversell it. The limits are in the post itself: model response time means seconds per look, so nothing here is fast; the agent struggles indoors and with no minimap, and Morrowind — a game with neither — struggled. Those are the constraints of a language model looking at screenshots and deciding what to press, and no amount of plumbing removes them.

The README is equally blunt about safety. Single-player and offline games only: do not use it in online or multiplayer games, or with any game protected by anti-cheat, or you will very likely be banned. vinput refuses to inject when it detects a known anti-cheat, but the README says plainly that the check is a courtesy, not a guarantee. The binaries are not code-signed, so antivirus software may flag them, and the disclaimer puts the risk — bans, lost saves, data loss — squarely on the user.

The thread’s sharpest question was not technical but philosophical: if the joy of a game is playing it, what is the point of having an agent play it for you? The creator’s answer is practical rather than grand — automating the tedious and repetitive parts, mod development, ports, simulations. That is the use case to take seriously, and it is also the one that keeps the demo honest: a tool for grinding through the boring bits, not a claim that AI plays games well.

A computer desktop with several small game windows running in the background behind a main work window, a robot hand resting on the keyboard
An editorial illustration of several games running in parallel behind a work window. AI-generated illustration.

Why it matters#

This is the latest in a run of Reddit demos where the model is the player, not the chatbot. A 4B model fetched a netherite ingot in Minecraft from a single sentence; Claude Sonnet built a six-year-old’s unicorn game in under a month; Opus 5.5 is building an endless Backrooms that never stops growing. This one is different in kind: it is infrastructure, not a one-off run. A general tool any agent can use on any supported game, with the plumbing — focus, input, capture, navigation — already solved.

The background-play property is the real shift. An agent that plays games has always had to occupy the machine it plays on. An agent that plays in the background can run alongside real work, several games at once, on hardware that is otherwise idle. That is what turns a parlour trick into a plausible piece of test infrastructure: overnight playtesting, mod validation, port checking, the repetitive runs nobody wants to do by hand. The model’s slowness is the bottleneck, not the plumbing — and model speed is the part that keeps improving.

What to watch#

Three things will decide whether this stays a viral weekend or becomes a tool people actually use. First, the profile library: 15 games is a start, and whether the community writes profiles for more — and whether they work without hand-tuning — is the real test of the “profile, not code” claim. Second, whether anyone wires it into a real playtesting pipeline, where the boring-bits use case meets a paying customer. Third, whether the anti-cheat line holds: the README’s warning is the part that matters most if this spreads, because the same DLL-injection trick that makes background play possible is exactly what anti-cheat systems are built to catch.

Until then, the fair description stands: a serious piece of plumbing, a fun video, a creator who states the limits before anyone asks, and a thread that spent its energy arguing about what the tool is for — which is usually the sign that the tool itself works.

Sources: the original post by u/Wonderful-Ad-8579 on r/ClaudeAI; the project on GitHub. Counts, tool numbers and technical claims are the creator’s own statements in the post, the comments and the project README, and commenter claims are reported as thread claims, not independently verified. The images are AI-generated editorial illustrations, not screenshots of the games.