Guide

Code while you play Final Fantasy XIV

Q: Which agent should I use?

Whichever you already use — Claude Code, Cursor's cursor-agent, or Codex all work the same way here. If you'd rather not install anything, Backgrind's hosted Grindy agent runs with nothing to set up.

Andrew Mercer June 21, 2026 · 5 min read

Final Fantasy XIV is a mmorpg with a lot of in-between time — and in-between time is exactly what an AI coding agent runs on. You describe a task, the agent works for a few minutes on its own, and you get back to the game until it needs you. Done right, a session of Final Fantasy XIV and a shipped code change happen on the same screen, at the same time. Here's how to set that up.

The downtime in Final Fantasy XIV

FFXIV hands you downtime constantly: Duty Finder queues (especially as a DPS), retainer ventures, crafting and gathering rotations, and long teleports between zones. The DPS queue alone can be a coding session.

Queue for a raid, fire off "add pagination to the search results endpoint," and check in when the duty pops.

The setup, start to finish

The whole trick is keeping the agent visible over the game and only hearing from it when it matters. Three pieces:

Run Final Fantasy XIV in borderless (windowed) fullscreen. An overlay can only draw over borderless mode — exclusive fullscreen hands the whole display to the game and hides every overlay at the OS level. It's a one-time toggle in the graphics settings; see borderless vs exclusive fullscreen for why.
Put your agent in an always-on-top window. Instead of alt-tabbing to a buried terminal, keep the agent floating in a corner — an always-on-top terminal you summon and hide with a hotkey.
Let it notify you. The point is to play, not watch a terminal. Set it up so the agent pings you only when it finishes or needs a yes/no — otherwise it stays out of the way.

Will it get you banned?

A terminal overlay is a plain always-on-top window — the same category as the Discord or OBS overlay. It doesn't read game memory, inject input, or hook the game process, so it isn't what anti-cheat looks for. The full reasoning (and the honest caveats) is in will a coding overlay get me banned? — the short version: a window that draws on top is not a cheat. As always, exclusive fullscreen is the only setting that actually breaks the overlay, not your account.

Keep your secrets safe while you're AFK

If the agent is running while your attention is on Final Fantasy XIV, you want guardrails on what it can touch. Mark your .env, keys, and anything sensitive as off-limits so they never leave your machine, and pre-approve only the safe commands so the agent runs free but the risky calls still wait for you. See pre-approval policies.

Frequently asked questions

Can I really code while playing Final Fantasy XIV? Yes — you use Final Fantasy XIV's natural downtime (queues, loading, travel, grinding) to fire off and review agent tasks. You're not coding mid-fight; you're using the minutes the game already makes you wait.

Which agent should I use? Whichever you already do — Claude Code, Cursor's cursor-agent, or Codex all work the same way here. If you'd rather not install anything, Backgrind's hosted Grindy agent runs with nothing to set up. See the 2026 field guide if you're choosing.

Do I need two monitors? No. That's the point of an overlay — the agent floats over Final Fantasy XIV on a single screen, and a hotkey makes it vanish when you want the full view.

Where Backgrind fits

Backgrind is the overlay this whole setup describes, in one app: it wraps your real agent (Claude Code, Cursor, or hosted Grindy) in an always-on-top window that floats over Final Fantasy XIV in borderless fullscreen, stays click-through when you want to see the game, and chimes only when the agent needs a decision or finishes. Fire off a task, get back to Final Fantasy XIV, and let the agent grind while you do. See it in the live demo, read the full how to run Claude Code while gaming walkthrough, or browse more games to code through.