Claude Code is a video game

A developer draws parallels between coding with Claude Code and playing video games like Civilization, Dota 2, and StarCraft, noting that the loop of prompting and responding in LLM conversations mirrors game mechanics. The author introduces a dice-rolling mechanic for Claude Code that triggers reflection and artifact generation, and contrasts the turn-based nature of chat with the continuous, multi-agent control of Claude Code sessions.

Claude Code is a video game The loop that keeps you playing Civilization runs under Claude Code, at higher resolution. Game design ports over, down to commanding several agents like an RTS. Three hours past bedtime. A quick bug fix had turned into a refactor, then a brainstorm, then a feature branch running in parallel, and I had not noticed the passing of time. This used to only happen when I played Civilization. “One more turn” is a meme any Civ player will recognize. You issue your commands, pick your policy cards, queue the next building in your capital, press next turn, and the world starts moving. Before you realize it you are handed a fresh puzzle: familiar in shape, filled with subtle novelties. So the loop continues. LLM conversations run on that same loop. You send a prompt, the model responds, and its response becomes the next prompt you reply to. Coding agents add tool use to the equation: the model can call functions and react to their results with the sophistication of a modern AI player, well past anything a rule-based computer player could do. The exchange starts feeling more like play than simple Q&A. You act, the world changes, you are handed a new situation. That loop is close enough to a tabletop that you can drop a game mechanic straight into it. cc-dice https://github.com/pro-vi/cc-dice rolls a die each time a turn ends, and the chance grows the longer a conversation runs. When a Natural 20 lands deep into a session, the stop hook prompts the agent to reflect on what happened /cc-reflection , extract the underlying pattern, and generate an artifact that improves the system going forward. The dice works, because the loop underneath was not much different from a D&D campaign. Porting a mechanic is the most literal borrowing. The deeper one is in the shape of the loop itself, and the first thing games vary is time. Civilization divides time into discrete turns and space into hexagonal tiles, in the spirit of Chess. Dota 2 runs in continuous time across a coordinate plane with near-infinite positional granularity. Beneath the surface, both games demand the same thing: manage resources, control space, and make optimal decisions under constraints. Yet resolution, the granularity at which they operate, transforms the entire feel of play. The same resolution shift separates chat from Claude Code. Chat is the card game: you play your hand, pass your turn, and wait for control to return. The turn is atomic, and you are locked out until it comes back. Claude Code runs closer to continuous time. You can steer mid-turn, interrupt a tool call halfway, feed new context while it is still working. The codebase becomes a navigable map, and tool calls are granular actions taken across several files at once. You are not waiting out a committed turn anymore. You are in continuous contact with a system that is still moving. That climb so far is on one axis: time. A card game or Civilization takes turns, and Dota 2 runs continuous. Yet Dota 2 and StarCraft share the same continuous clock and still feel nothing alike, because an RTS hands you a second axis. In Dota 2 you pilot one hero, your full attention on a single unit, one set of cooldowns, one role to perform. StarCraft makes you command an army. You give orders to each unit, peel a group off to harass, queue production in one base while a fight breaks out in another, and your attention is spread across a dozen things that all keep moving whether or not you are looking at them. Same real-time clock, far more of it under your hands at once. A single Claude Code session is the Dota 2 version. One agent, one hero, your whole attention resolving onto its next move. Running several at once is the StarCraft version. You hand one a refactor, send another off to write tests, glance at a third halfway through a migration and check whether it is on track. You shift from piloting a single spell-caster to commanding an army: which unit demands attention now, which can proceed without you, which is heading for disaster. You are above the map, deciding where to look next. That last part is the one I worry about. One agent kept me up three hours past bedtime. I now run seven.