Working with an AI agent

Connect an AI agent, such as Claude Desktop, and it can make missions in the studio while you watch. You talk to it in its own window; everything it does appears on the map as it happens, and undo works as usual.

It uses your agent's own account and plan, not the studio's AI settings. The AI designer inside the studio stays, and it's still handy for quick changes to a selected area. The two share the same tools.

Connecting

1. Open the studio and press MCP, at the top.
2. Press Start.
3. Connect your agent. You only do this once for each program:
   • Claude Desktop: press Add to Claude Desktop. If Claude Desktop is open, the studio asks you to quit it first (closing its window isn't enough: use Quit from its icon near the clock), and adds it as soon as it has closed. Then open Claude Desktop, and igi-studio appears among its connectors.
   • Claude Code: copy the command shown and run it in a terminal.
   • Anything else, such as Cursor or VS Code: copy the settings shown into its MCP settings.

The agent can only reach the studio while it's open and started. If you ask it for something with the studio stopped, it tells you to press Start. Stop ends it straight away. The studio remembers whether you left it on.

Only programs on your own PC can connect.

Asking for a mission

Tell it what you want, for example: "Make a stealth mission on the Trainyard map: a guarded compound with the objective inside, and two ways in."

A good agent will look at the maps, show you a plan, and wait for your word before building. It then builds one area at a time, looking at each from above and in 3D, and tries it in the game.

Select something on the map and you can say "this" in your conversation: the agent can see what you selected.

What it can do

Nearly everything you can: choose a level, build, place guards and patrols, set objectives and events, shape and paint the ground, make cutscenes, and write the texts. It can see the map and the 3D view as pictures, and it can copy whole areas out of the game's own levels.

It has no way to touch your community account, your sign-in, your API keys or the studio's settings. If it wants to delete a mission, the studio asks you first.

Testing in the game

The agent can try a mission in the real game, and see it through the game's own camera. It does this in a test copy of the game, made beside yours the first time (about 4 GB, named IGI-Test). Your own game isn't touched by tests.

While a test runs, about a minute:

• A game window opens, 1024 x 768.
• Your mouse and keyboard stay yours: the studio sends the game its keys directly. Only for a picture of the map computer does the game come to the front, for a moment.
• Leave the game window open. It closes by itself.

If your own game is running, the test waits for you to close it: only one copy can run at a time.

When the agent is ready for you to play, it can also apply the mission to your own game, as Apply to game does.