Contents ≡

Wiki/Session notes

Session 4 · Start Unity MCP with Plan

  1. 1Why this matters especially in Unity
  2. 2One round
  3. 3What to say
  4. 4What to look for in the plan
  5. 5When it misses
  6. 6Keeping the plans
  7. 7Where this comes from

Start Unity MCP with Plan

When you build a scene with Unity MCP, first make a plan in Cursor's Plan mode, read it, and only then run it. A single sentence can make the AI create dozens of objects and change materials and scripts all at once. Seeing what it will do ahead of time and choosing is the easiest way to keep the scene going where you want.

Connecting and undoing are covered in Session 4 · Picking Unity back up. This page is about what comes after you're connected.

Why this matters especially in Unity

Cursor can roll back code files for you. But Unity MCP edits the open scene directly. Objects it created, deleted or moved don't come back with Cursor's Restore.

So the few minutes you spend reading the plan before running it save you an hour later. A plan is a single page of text, so you can revise it as many times as you like, and the scene stays as it is while you do.

One round

  1. Save the scene. Ctrl+S (Cmd+S on a Mac). If the plan goes wrong, you come back to this point.
  2. Switch to Plan mode. In the chat input, press Shift+Tab until Plan appears. You can also pick Plan from the mode selector under the input.
  3. Describe the scene you want as a result. You don't need to say which tools to use. Write what is seen, what moves, and the mood.
  4. Answer the AI's questions. It will ask about things you haven't decided, like size, color or how many. If you don't know, you can answer "decide for me, but write it in the plan."
  5. Read the plan. Check the points under "What to look for in the plan" below. If you don't like a step, ask for a change in the chat or edit the plan document yourself.
  6. Build. Unity only starts changing when you press the plan's Build button. Nothing changes until then.
  7. Check in Unity and save. If it came out as you wanted, save the scene and move on to the next plan.

What to say

If you're starting from a poem, it might go like this.

I want a scene where twenty small lights slowly rise above dark water. The lights are a warm orange and fade as they go up. The camera is close to the water, looking up. Keep everything that's in the scene now and add to it.

The last sentence matters. If you say up front what to keep, the plan will have fewer steps that delete things.

What to look for in the plan

  • Are there steps that delete or change things? If a line deletes or overwrites objects you already made, check whether that's really okay. Look here first.
  • What gets created, and how many? If object names and counts are written down, you can find them in the Hierarchy after the build.
  • Does it create new scripts? Movement usually goes into a script. If you know the script's name, you can later point to it, as in "just slow down the speed in that script."
  • Does it install packages? Installing takes time and changes project settings. Ask whether it's really needed.
  • Is the plan too long? If it has more than ten steps, split it in two. The ground and water first, the lights in the next plan. The shorter the pieces, the easier it is to see where things went off.

When it misses

If the build result isn't what you pictured, don't keep piling fix requests on top of it. As fixes stack up, the scene gets more tangled and you can't tell what caused what.

Instead, go back to the saved scene, revise the plan, and build again. Close the scene without saving and reopen it, and you're back to the state you saved in step 1. You now know what went wrong, so write that into the plan as one line.

If only one small thing is off, it's fine to switch back to Agent mode and fix it with one line. That's for when the change is clear, like "just make the lights half the size."

Keeping the plans

By default, plans are saved in the home folder on your computer. Click Save to workspace above the plan to move it into the project folder.

Plans you keep become a record of your work. What you asked for in what words, and what you revised and redid, stay in order. They are ready-made material when you fill in your production plan or write about your work after the December exhibition.

Where this comes from

Starting Unity MCP with Plan mode is Joonhyung Bae's recommendation. Bae came up with it while sitting in on Session 4, and it is separate from what director Seoyeon Hong taught in class.

How to use Plan mode follows Cursor's official documentation, Planning. Going back and revising the plan when a build misses is also that documentation's recommendation.

Materials for 2026 Open Circuit Busan: Art & Tech Practice · Written and planned by Joonhyung Bae