Guides
Roblox Assistant: when to let it act, and when to plan first
Roblox Assistant's default (Agent) mode vs Planning Mode: what each does, when to use which, and how to write a plan that builds well.
3 min read

Quick answer
What's the difference between Agent and Plan in Roblox Assistant?
In the default mode, often called Agent, Assistant acts on your request straight away, editing scripts and objects. In Plan mode it studies your game, asks questions and writes an editable plan first, and nothing changes until you click Build. Use the default for small edits and Plan for anything with several steps.
The two ways to work
Roblox's Assistant guide describes Planning Mode, which you switch on by choosing Plan in the dropdown of the Assistant input panel, or by typing /plan. The other choice is Assistant's normal mode, where it acts on requests directly. Creators often call that Agent mode.
- What happens: Default (Agent): Assistant makes changes as it works; Plan: Assistant writes a plan, and you approve it
- Asks questions first: Default (Agent): Sometimes; Plan: Yes, it studies code and data model and asks clarifying questions
- Output: Default (Agent): Changes in your place; Plan: An editable Markdown plan
- Runs automatically: Default (Agent): Yes; Plan: Never. Only when you click Build
- Best for: Default (Agent): Small, clear edits; Plan: Features, systems, anything multi-step
When to use the default mode
- "Anchor every part in the Map folder."
- "Rename these scripts to match their purpose."
- "Fix the error on line 42 of CoinScript."
- "Insert asset 12345 and put it at the spawn."
Small, clear, easy to undo. Planning would only slow you down.

When to plan first
- A new system: rounds, shops, inventories, data saving.
- Changes that touch many scripts or objects.
- Anything you'd explain to a teammate in more than two sentences.
- Work where a mistake is hard to undo.
Roblox's April 2026 announcement called the plan "a mini game design document" (Roblox Studio going agentic). Read it the way you'd read a teammate's proposal.
Writing a request that plans well
Give Assistant what a teammate would need:
- Goal. "Players collect coins that respawn every 30 seconds."
- Where. "Coins are in Workspace.Coins. Leaderstats already exist in ServerScriptService.Leaderboard."
- Rules. "Server-authoritative. No client-side coin counting."
- Done means. "A player touching a coin gains 1 coin, it disappears and comes back 30 seconds later."
Then edit the plan. Remove steps you don't want, fix wrong assumptions about your game, and add anything missing. Plans are saved as Markdown, so changing a line is quick.
After you click Build
- Watch what changes, and stop it if something's going wrong.
- Playtest. Roblox's own guide warns generated scripts "might not function flawlessly". The playtest agent, in beta, can help check the result against the plan.
- Save a version once it works.
Plan mode and your usage limit
A good plan often saves usage. One clear plan and one build costs less than a string of small requests and corrections. See Assistant daily limit.
Planning across tools
Plans aren't only for Assistant. If you also use Claude Code or Cursor through Studio's MCP server, the same plan can guide them. Roblox describes plans as something "agents can use to execute tasks in parallel". See build Roblox games with Claude.
Assets for the plan
Plans often include steps like "add 10 crystal props to the cave". For props in your own style, from a sketch or reference, Vi3W generates textured, retopologised meshes and exports GLB, FBX or OBJ to import before you build. Make props in Vi3W.
Last reviewed

