Set Up Your Gaming PC for Modding with an AI Agent | AI Guides

How to turn Claude Code or Codex into a careful modding assistant on your own gaming PC. It reads mod files, installs and checks downloads, backs up your saves, and keeps notes, while you make the calls. You do not need Zo. You need a Windows gaming PC, a Claude or ChatGPT plan, and a game you like to mod. This guide teaches the setup and the habits, not any one game or mod. Where a step here disagrees with the official page linked next to it, the official page wins.

Hand this guide to your AI

You can read this yourself, or let your AI walk you through it:

Click Copy for your agent at the top of this page (or download the .md) and paste it into your agent.
Download the workshop rules file: modding-workshop-rules.md. You will put it in your modding folder in Step 2.
Send this prompt:

I want to set up this PC for modding with your help. Follow the guide I just pasted, one step at a time. Before each step, tell me in plain English what you are about to do and why. Ask me before you delete, move, or overwrite anything. Start by finding out which games I have installed, where their mods and saves live, and how much free disk space I have.

Note for AI agents: Work through this guide with the user step by step. Treat their saves and current mod setup as irreplaceable: back up and verify before any change, never delete without explicit approval, and record what you changed in their records folder. If you cannot do a step (a login wall, a permission prompt), say so and hand that step to the user.

Why use an agent for modding

Modding is mostly careful file work: reading readme files, checking which game version a mod needs, unpacking archives into the right folder, keeping a working setup working, and figuring out what broke when it stops. An agent is good at exactly that. It can read every file in a mod in seconds, compare versions, check a download against its published checksum, and keep a written record of every change.

You stay in charge of the fun part: which mods, which playthrough, what kind of world you want.

What you need

An AI coding agent and a plan. Claude Code (needs Claude Pro or higher, see claude.com/pricing) or Codex (needs a ChatGPT plan with Codex, see chatgpt.com/pricing). If you have never installed one, do Claude Code and Codex: Setup for Beginners first. It takes about ten minutes.
The agent installed on the gaming PC itself. It needs to see your game files, so install it on the machine you play on, not a laptop next to it.
A mod site account. Most mod sites, Nexus Mods included, need you to be logged in to download. Your agent cannot log in for you, so you download and it handles everything after that.
Free disk space. Mods, backups, and original downloads add up fast. A big mod list can need tens of gigabytes. Your agent can tell you where your space went.

Step 1: Let your agent map your setup

Open a terminal, start your agent, and ask it to look around before it touches anything:

Without changing anything, map my gaming setup: which game stores and games are installed, where each game's mod folder and save folder are, which mods are installed for [game], and how much free space each drive has. Write what you find to a notes file I can read.

What it will usually find: Steam games live under C:\Program Files (x86)\Steam\steamapps\common\ by default. Saves are usually in Documents\My Games\, in Documents\ under the game's name, or in %LOCALAPPDATA%. Mods live wherever the game or your mod manager puts them.

If you already use a mod manager like Vortex or Mod Organizer 2, keep using it. Tell your agent which one, so it works with the manager's folders instead of around them.

Step 2: Build a modding workshop folder

Make one folder, outside the game and outside your user folders, for everything about modding except the running game. For example C:\Modding, with:

archives for the original downloads, untouched, so you can always reinstall the exact version.
staging for unpacked mods you are checking before you install them.
backups for save and settings backups, one dated folder each.
records for your mod list, what you changed, and what broke.
tools for helper programs like 7-Zip.

Mods still run from the game's own folder. The workshop is where you keep the originals, the backups, and the record.

Now put the rules file in it. Save modding-workshop-rules.md into the workshop folder and rename it CLAUDE.md for Claude Code or AGENTS.md for Codex. Your agent reads that file automatically whenever you start it in that folder, so the safety habits in this guide become its default behavior. Fill in the "About my setup" section at the top, then start your agent from the workshop folder from now on.

Step 3: Back up before every change

This is the one habit that makes everything else safe. Before you add, remove, or update a mod, ask your agent to back up:

your saves for that game,
the game's settings and mod-list files,
any mod data that lives outside the save, such as an AI or companion mod's memory folder.

Then ask it to check the backup against the originals, file by file. A backup nobody checked is a hope, not a backup. Ask it to leave a short restore note inside the backup folder, so future you knows how to put things back.

Make a named save before big changes, too. Many games share autosave slots across playthroughs, so a new playthrough can quietly overwrite an old autosave.

Step 4: Freeze the game version

Game updates are the most common thing that breaks a working mod list. Mods are built for a specific game version, and an update can land overnight.

On Steam you have two controls:

Only update when you launch. Right-click the game, choose Properties, then Updates, and set automatic updates to Only update this game when I launch it. This stops surprise background updates, though Steam may still ask for the update before it lets you play.
Stay on an older version. Some games offer older versions under Properties, then Betas. If yours does, pick the version your mods are built for. Ask your agent to read each mod's requirements first, so you pick the right one.

When you do want to update, back up first (Step 3), update, and check each mod's page for a version that matches.

Step 5: Install mods with your agent

You download, your agent does the rest:

Download the mod into your Downloads folder and tell your agent its name.
Ask it to move the original into archives, unpack a copy into staging, and read the mod's readme and requirements.
Ask it to check: Does this mod need other mods? Does it match my game version? Does it include copies of the game's own files? Does it conflict with anything I already have?
If the mod page publishes a checksum, ask it to compare that to your download.
Only then install it, add it to your mod list, and write the change in your notes.

Add mods a few at a time and launch the game in between. If something breaks, you will know which batch did it. When a Modded Game Crashes covers what to do then.

Step 6: Keep more than one setup

Once you have a setup you love, you may want a second one, for example a different total-conversion mod. You do not have to choose. Ask your agent to:

save a copy of your current mod list (the launcher's or mod manager's list file) as a named profile,
build the second profile,
write a small switch script plus a desktop shortcut for each profile, so one double-click swaps the mod list and starts the game.

Check whether your mods keep per-playthrough data in separate folders. Many AI and companion mods file their data under a playthrough ID, which keeps two campaigns apart, but confirm it before you start the second one.

Windows snags to know about

Controlled Folder Access. A Windows ransomware protection that blocks programs from writing to Documents, Desktop, and Pictures. If your agent's writes fail with an access error, this is often why. It lives in Windows Security under Virus and threat protection, then Ransomware protection. Allow the specific program rather than turning the protection off.
OneDrive backing up Documents. If OneDrive syncs your Documents folder, your game saves are in the sync too, which can cause slow saves and conflicts. Ask your agent whether your save folders are inside OneDrive.
Running out of space. Shader caches, replay files, and old mod downloads pile up. Your agent can list the biggest folders and explain each one before you delete anything.
Blocked downloads. Windows marks downloaded files as coming from the internet, and some games refuse to load mod files marked that way. Your agent can check for that mark and clear it.

Keep your agent's memory

Your agent's conversation history is a record of every change you made together. Claude Code deletes old session files after 30 days by default. To keep them for a year, ask it to add "cleanupPeriodDays": 365 to its settings file at %USERPROFILE%\.claude\settings.json. Session files are small, around a megabyte each.

Keep the records folder current as well. Ask your agent to update your mod list and change log at the end of every session. Next time, it reads those first and picks up where you left off.

What your agent will not do

Log in to mod sites or stores for you. You download, it installs.
Delete or overwrite without asking, once the rules file is in place. That is on purpose.
Upload your files off the PC. Agents often refuse to send files from your machine anywhere else, even to your own server. That is a safety feature. Move those files yourself.
Guarantee a mod works. It checks everything it can see, then you test in the game.

When a Modded Game Crashes: Let Your Agent Investigate
Make Mods Your Own: Read, Tweak, and Write Mod Content with an Agent
Plugins, Skills, and MCP, for giving your agent more abilities.
Game-specific modding guides: mod links, load orders, and real fixes for Bannerlord, Starfield, and more.