How to use AI in Roblox Studio

Option 1: the assistant already in your copy of Studio

Roblox ships an assistant inside Studio. It is free, it is already installed, and it is the correct first thing to try. There is a usage cap on it and Roblox does not publish how big that cap is, which is the one detail you cannot check before you start. Spend twenty minutes with it before you install anything, because you will learn more about what you actually need from that than from any comparison page, this one included.

Studio also has an MCP server built into it, with a quick-connect for Claude Code, Cursor, Codex and the Gemini CLI. If you already pay for one of those, you can point it at Studio for nothing extra and skip this entire category of product. We are not going to pretend that option does not exist.

And since February 2026 you can put your own Anthropic, OpenAI or Gemini key into Studio and have the built-in assistant run on a frontier model. If you have a key already, or you are willing to make an account and pay per token, that is the cheapest good answer available and you should take it before you read the rest of this page.

Option 2: add a plugin

The reason to add a third-party plugin is almost always the model, not the tooling. If the built-in assistant is producing Luau that does not compile and you do not want to manage an API key to fix that, a plugin that includes a frontier model in its price is the thing you are shopping for. That is the whole category, and the rest of this section is our own tool, so read it knowing whose page you are on.

RoCreator is a free Studio plugin that writes real Luau into the place you already have open. Nothing runs outside Studio, the code is yours afterwards, and the setup below is 7 steps end to end. We are counting them out rather than rounding them down, because the single most common failure in this category is a setup guide that quietly skips the step where people get stuck.

Setting it up, all 7 steps

Both paths below are free and neither needs a card. Steps 2 to 7 happen inside Studio.

1. 1Make a free account and generate a connection code. It is the one step that happens in a browser, and it is what tells the plugin which project to write into.
2. 2Download the plugin file.
3. 3In Studio, open the Plugins tab and click Plugins Folder. That opens the exact folder Studio loads plugins from, so there is no path to type: Plugins → Plugins Folder
4. 4Move RoCreator.rbxm into that folder. To get there without Studio, paste the path below into Explorer's address bar on Windows, or Finder's Go to Folder box on Mac, rather than clicking through folders. On Windows: %LOCALAPPDATA%\Roblox\Plugins On Mac: ~/Documents/Roblox/Plugins
5. 5Restart Studio, or reload from: Plugins → Manage Plugins
6. 6In Studio, click the RoCreator button in the Plugins toolbar to open the link panel.
7. 7Paste the code from step 1 into the session token field and click Link.

The step people get stuck on is moving the file. That folder path is not something you can click your way to, because it contains a Windows variable and it lives inside a folder Windows hides by default. Paste the path into the address bar rather than browsing for it, or use Studio’s own Plugins Folder button, which opens the exact directory with nothing to type.

The order looks backwards and is not: you open Studio to find the plugins folder, then restart Studio after the file is in it. Studio reads that folder once at launch, so the restart is what actually loads what you just put there.

How to write a prompt that lands

Name the thing. Do not select it. What the plugin sends is a walk of your Explorer tree, the same names and classes you see in the panel on the right, and it never reads which object you happen to have clicked. So “make the door open when a player touches it” works and “make this open” is a guess. If two objects share a name, rename one before you prompt, because you are the only one who can tell them apart.

Then go small. The instinct is to write a paragraph describing a whole system, and it is the wrong instinct: a long first prompt is the slowest thing you can ask for and the most likely to come back wrong in a way you cannot locate. Ask for one change, look at it, then ask for the next one. The loop is the point.

Four prompts, four seconds of typing, and the third one is a correction. Correcting the tool in three words is not a failure of the tool or of you. It is the normal shape of the work, and any guide that shows you one perfect paragraph producing one perfect result is showing you a demo rather than a workflow.

What happens when it runs

What no prompt will do for you yet

No terrain and no landscapes. Ask RoCreator for a mountain and it will tell you to open Studio’s Terrain Editor, which is free, built in and better at it than a sentence would be. That is a decision rather than a gap we are working on, and it is why the guidance above is to build the place yourself and prompt for the code.

And no 3D model generation. There is a text-to-3D path inside RoCreator, it has worked, and it is switched off: the outside service it uses has no credits on our account, so nothing is routed to it and the server refuses the command outright rather than queueing a job that could never finish. What you actually get when you ask for a barrel or a treasure chest is either an object built out of ordinary parts, or a script-free model found in the Roblox Toolbox and inserted into your place. Both are real results. Neither is a generated mesh, and if a generated mesh is what you need, this is not the tool to pick for it today.

No tool in this category can press a key for you. A Studio plugin is not allowed to, which means a sprint that only misbehaves when you actually hold Shift will pass every automatic check that exists. So playtest the thing yourself before you ship it, and ask any tool that claims it proved the fix which inputs it pressed.

And none of them will hand you a finished game from one sentence. What they are genuinely good at is putting one working feature into a place you already own, over and over, faster than you could type it. That is a smaller promise than the category usually makes and it is the one that survives contact with a real project.

Questions people actually ask