Guide

How to run Claude Code while playing a game

AI coding agents changed the shape of a coding session. You give Claude Code a task, and for the next five to twenty minutes it greps, edits, runs tests — and occasionally stops to ask permission. You're not coding anymore; you're waiting with interruptions. That's exactly the kind of time a game is for. Here's how to run Claude Code while playing a game without alt-tabbing every ninety seconds — and without getting banned.

The babysitting problem

Agents are autonomous right up until they aren't. Claude Code stops for a yes/no on a risky command, hits a question about your intent, or finishes and waits for the next task. If the terminal is buried behind a fullscreen game, you find out minutes later — the agent sat idle while you cleared a dungeon. Alt-tab to check it, and the game minimizes, stutters, or drops you out of the action.

So the goal is: see the agent's state at a glance, get pinged when it needs you, and answer without leaving the game.

Option 1: a second monitor

The classic answer, and it half-works. The terminal lives on monitor two; you flick your eyes over occasionally. Problems: you don't notice when the agent stops (no sound, no flash — just a quiet prompt sitting there), clicking the terminal steals focus from the game, and plenty of people game on a laptop or a single ultrawide. A second monitor gives you visibility, not notifications.

Option 2: an always-on-top terminal overlay

The better answer is the one Discord and OBS already use: an always-on-top overlay window floating over the game. Your agent's terminal renders in a translucent window in the corner of the screen — you watch it work between fights, and it stays out of the way the rest of the time.

This is what Backgrind does. It wraps the real Claude Code CLI (or Codex, or Cursor's CLI — it's your login, your history, your config) in a floating window with a terminal, a file tree, and one crucial addition: ambient notifications. When the agent needs a decision, the window flashes and chimes. Otherwise it never interrupts. You can try a simulated version in the live demo.

The one setting that matters: borderless fullscreen

Overlays can't draw over exclusive fullscreen — in that mode the game owns the display and nothing else gets composited on top. The fix takes ten seconds: in your game's video settings, switch Display Mode from “Fullscreen” to “Borderless” (sometimes “Borderless Window” or “Windowed Fullscreen”). It looks identical, tabbing is instant, and on modern Windows the performance difference is negligible. Nearly every current game has the option — WoW, League, Dota 2, Fortnite, Baldur's Gate 3, you name it. We unpacked the details in borderless vs exclusive fullscreen.

“Will this get me banned?”

Fair question, and the answer hinges on how the overlay works. Anti-cheat systems care about programs that read game memory, inject code into the game process, or automate input. A plain always-on-top window does none of that — it's the same OS mechanism as the Discord overlay or a picture-in-picture video. Backgrind deliberately never reads game memory and never injects input; the game just runs underneath an ordinary window. See the FAQ for the longer version.

Don't leak your secrets while you're AFK

One thing to set up before you let any agent grind unattended: keep credentials out of its reach. Claude Code respects ignore rules, and Backgrind adds a .grindignore file — paths listed there (your .env, key files, infra configs) never leave the machine, no matter which model is doing the work. Write it once per repo and forget about it.

The setup, start to finish

1. Switch the game to borderless fullscreen in its video settings.
2. Launch Backgrind and point it at your CLI — it runs your existing claude login, so there's nothing new to authenticate.
3. Give the agent a real task — “fix the flaky login test”, “refactor the auth middleware”, a backlog ticket.
4. Play. The overlay sits translucent in a corner. A hotkey hides it; another makes it click-through so your mouse hits the game.
5. Answer when it pings. Flash + chime means the agent needs a yes/no or finished. Type the answer, get back to the fight.

What it feels like

The surprising part isn't the convenience — it's the throughput. An agent that gets answers in seconds instead of minutes finishes multi-step tasks dramatically faster, because its idle time was always your response time. Queue up tasks before a raid, answer three prompts between pulls, and the backlog is shorter when you log off. Code while you grind.