In short
To use AI in Roblox Studio, click Assistant on the right side of the bar along the top of Studio, select the object you mean, and type what you want. Assistant is built in, needs no setup, its docs list no price, and it can write scripts and change objects in the place you have open. Pick Plan in its dropdown, or type /plan, to get a plan you can edit before it builds anything.
- Want your own AI client instead? Studio's built-in MCP server connects Claude Code, Cursor, Codex and others, and Roblox's official agent plugin connects it to Claude and ChatGPT.
- Third-party plugin agents such as RoCode edit your place too, and RoCode gives free credits every day. A chatbot in a browser tab sees only what you paste.
- Not sure which fits? Which tool for which job matches common tasks to a route.
- Whichever you pick: save a version first, ask for clear, small changes, read every change, and play-test it yourself.
On this page
How to use Roblox Assistant, step by step
Assistant is Roblox's own AI helper, built into Studio. It answers questions, creates and changes objects and scripts in your place, inserts Creator Store assets, explains code, and generates materials, 3D meshes and procedural models. Roblox's AI overview also lists running code, simulating input and playtesting among its abilities.
How to use Assistant in Roblox Studio
- Update Roblox Studio to the latest version.
- Click Assistant on the right side of the mezzanine bar, the strip along the top of the Studio window.
- Select the object you mean first. A new script goes into the selected object; with nothing selected, Assistant decides where it goes.
- Type a request. For a bigger job, switch the dropdown in the input panel from Agent to Plan, or type
/plan. The plan is a Markdown document you can open and edit, and nothing is built until you click Build. - Read what it changed, then press Play and test it yourself. If a long build stops with "The current response exceeded the maximum output length", click Continue.
- For a new task, open the chat list and choose New Chat: each chat has its own context window. To try another direction without losing this one, click the branch icon under a reply.
Agent, the default, works on your place as it goes. Plan writes the steps first, and a plan never runs on its own. Chat history is saved in the cloud for each place, so your chats are still there after you restart Studio.
Slash commands
| Command | What it does |
|---|---|
/plan | Turns on Planning Mode: a plan you can edit before anything is built. |
/generate_mesh | A textured 3D mesh from a text prompt or a reference image. Select a Part first to use it as a bounding box. |
/generate_procedural_model | A model that updates itself when you resize it or change its settings. Up to 50 in a rolling 24-hour window. |
/generate_material | A custom material, applied to existing parts. |
/insert_asset | Inserts an asset by its ID. |
/segment_mesh | Splits a selected imported MeshPart into up to five named parts. In early preview. |
Skills (…, Assistant Settings, then the Skills tab) teach it your conventions. To use your own model, open …, Manage API Keys, add a key from Anthropic, OpenAI or Google Gemini and pick the model in the Model dropdown; usage then runs on your key, at that provider's prices.
Tips and limits
Roblox's docs warn that a generated script might not work flawlessly and that results vary each time you ask. Assistant also leans towards changing things at edit time: if something should happen while the game runs, ask for "a script that sets the time to 8:00 AM", not "set the time to 8:00 AM". The docs publish no price and no message limit; their one stated cap is 50 procedural models in a rolling 24-hour window. If Assistant stops answering or says you have hit a limit, see Assistant limits and errors.
Is the Roblox Studio Assistant good?
For something built in with no setup, it covers a lot: it edits your real place, can plan before it builds, and generates meshes, materials and procedural models. It is the sensible first thing to try. Its weak spots are the ones Roblox names: results vary, scripts need checking, and it can confuse edit time with run time. Treat what it makes as a fast first draft.
The four ways to use AI in Roblox Studio
Assistant is one of four shapes AI tools for Roblox take. The shape decides whether the AI can see your Explorer, whether it can make changes without copy and paste, and whether it can play the game to check its own work.
| Route | Edits your open place | Setup | Read more |
|---|---|---|---|
| Assistant, built in | Yes: scripts, objects and Creator Store assets. It can playtest. | None. | The steps above, and limits and errors |
| Studio MCP server + your AI client | Yes: scripts, running Luau, playtests, input and screenshots. | Turn the server on in Assistant, then connect Claude Code, Cursor, Codex or another client. Roblox's agent plugin connects Claude and ChatGPT. | Studio MCP guide |
| Plugin agent, such as RoCode | Yes. RoCode: scripts and instances, with a compile check in Studio, and playtests with plugin 3.9 or newer. | RoCode: free account and a Creator Store plugin; Studio connects by itself on the same Roblox account, or with a pairing code. | Roblox AI tools compared |
| Chatbot in a browser tab | No. It sees only what you paste. | None. | Using a chatbot well |
What each route costs, including every free tier, is compared in free AI for Roblox Studio.
Which AI tool for which job
The four routes overlap, but each is clearly best at something. Start from what you want done today, not from the model. Every row below rests on what this page already cites: Roblox's docs for Assistant, the MCP server and Build, and RoCode's own published facts.
| You want to | Best fit | Why |
|---|---|---|
| Explain an error, or review a script you paste in | Any route, a chatbot included | It only needs the text. Paste the exact Output line with the script path. |
| Write or fix one script in the place you have open | Assistant, or Code Assist while you type | Built in, no setup, and it sees the object you select. |
| Make a 3D mesh, a material or a procedural model | Assistant's slash commands | /generate_mesh, /generate_material and /generate_procedural_model are Assistant features. RoCode, for one, does not generate meshes. |
| Change many scripts and objects across your place | Assistant, an MCP client or a plugin agent | All three edit the open place directly. A chatbot would need every script pasted in and out. |
| Use the AI app you already pay for, such as Claude, ChatGPT or Cursor | Studio's MCP server, or your own API key in Assistant | The server is part of Studio; the client and its plan are your own. |
| Keep scripts in files with Git or Rojo | An MCP client with Script Sync | Roblox's coding harness guide pairs Script Sync, MCP and Git. |
| Build a playable first version from a description | Assistant's Plan mode, or a plugin agent | Plan writes the steps for you to edit before anything is built; an agent such as RoCode builds one system per prompt. Ask for a playable core first. |
| Have the AI play the game to check its work | Assistant, an MCP client, or RoCode with plugin 3.9.11 or newer | All can start a playtest. You still play it yourself: none can tell you whether it is fun. |
| Make a game on a phone | Roblox's Build tab in the mobile app | Studio needs a computer. Build makes simpler 2D and 2.5D games and is rolling out by region. See On a phone. |
Whatever you pick, the same rule decides whether the result is safe to ship: the server must decide anything involving currency, damage or saving. The checklist below lists what AI most often gets wrong, and the script guides show the server-checked version of common systems, such as a sword, a gun or a simulator.
Your own AI client through Studio's MCP server
MCP (Model Context Protocol) is an open standard that lets an AI client use tools in another app, and Roblox Studio has an MCP server built in. Turn it on, and an AI client you already use can work on your open session: explore the Explorer tree, read and edit scripts, run Luau, start and stop playtests, read the Output, capture the viewport and send keyboard or mouse input.
To turn it on, open Assistant, click …, then Manage MCP Servers (Settings, then MCP Servers, in newer versions), and turn on Enable Studio as MCP server. Quick connect then covers Antigravity, Codex CLI, Claude Code, Claude Desktop, Cursor, Gemini CLI and Visual Studio Code; other clients that support MCP over standard input and output connect with a JSON configuration or a command. Setup for each client is in the Studio MCP guide, and we have step-by-step setups for Claude Code, Codex and Cursor or VS Code.
Roblox's official agent plugin
Roblox also publishes an official plugin for AI assistants on GitHub, Roblox/roblox-studio-agent-plugin, under the MIT licence. Its README lists Claude Code, Cowork in the Claude desktop app, the ChatGPT desktop app and the Codex CLI. The plugin has no code of its own, only configuration and skill instructions: it runs the MCP server that comes with Studio, and you still turn that server on yourself. Once it is installed, ask your assistant "Get me set up with Roblox Studio". Because the server runs on your computer, claude.ai on the web and ChatGPT on the web or a phone cannot connect to Studio. Checked 22 October 2026.
Cost. The server is part of Studio. The AI is not: the client and its model come on their own terms, whether that is a free tier, a subscription or pay-as-you-go API use.
Limits. It takes the most setup of the four routes: a separate app, the server switch and often a restart. How well it works depends on the client and model you connect.
Plugin agents such as RoCode
A plugin agent is a third-party AI agent that works in Studio through a plugin. Like Assistant it edits your real place, but the chat, the models and the pricing come from another company.
RoCode is one of these: you describe a change in the web chat at rocode.app, and its free Creator Store plugin builds it in your open place, compile-checks the scripts inside Studio and marks each batch of changes as one undo point. With plugin 3.9.13 or newer the plugin connects by itself when Studio is signed in to the same Roblox account you use on RoCode; otherwise you type the 8-character pairing code from the plugin panel into the chat. The free Starter plan gives 1 credit a day. Pro is $9.99 a month in US dollars, before tax, for 150 credits. With plugin 3.9.11 or newer, RoCode can playtest your game in Studio and control a test character to check it works. Requests go through RoCode's server and OpenRouter to third-party models; RoCode is an independent product, not affiliated with, endorsed by or sponsored by Roblox Corporation.
It does not generate meshes, textures or animations from scratch or sculpt terrain by hand (it can build Terrain such as hills, lakes and islands with a generated script). It designs scenery, buildings and props new for each game, places free Creator Store models it finds by searching with your words when you ask for ready-made or realistic ones (with any scripts inside removed), and can insert a model, decal or mesh from an asset ID or Creator Store link you give. With plugin 3.9.14 or newer it takes screenshots of what it built, in edit mode, to check how it looks. The RoCode docs have the details.
Other agents work differently. By their own sites on 22 October 2026, Ropilot is a desktop app that installs its own Studio plugin, and ForgeBlox (named Forge until October 2026) is a Windows app that connects through Studio's MCP server; both run playtests. See RoCode vs Ropilot, RoCode vs Forge and the Roblox AI tools comparison.
A plugin runs inside Studio with the permissions you grant it, and one allowed to inject scripts can change any script in the place, so install plugins only from creators you trust, and disable the ones you are not using.
A chatbot in a browser tab
The simplest option is a general chat app such as ChatGPT, Claude or Gemini. There is nothing to install, and it is good at explaining a concept, walking through an error message, reviewing a script you paste in, or planning how systems should fit together before you build.
Its limit is that it cannot see your place. It does not know your door sits in a folder called Doors, or that you already have a leaderstats script, so it guesses paths and may write a second copy of a system you already have. You then create the right kind of script in the right place and paste the code in yourself.
To get more out of it, paste the full Explorer path of every object involved, the scripts it has to work with, and whether the code runs on the server or the client. If you are unsure which side code belongs on, read Script vs LocalScript vs ModuleScript first.
Can you use AI in Roblox Studio on a phone?
Not in Studio itself. Roblox Studio runs on Windows and Mac, so Assistant and the MCP server need a computer. On a phone, the Build tab in the Roblox mobile app turns a description into a game. Roblox's docs say Build focuses on simpler 2D and 2.5D games, is for age-checked users 9 and older, and is rolling out gradually by region, starting with New Zealand. A chat app on a phone can help you plan and write Luau but cannot connect to Studio, and RoCode's chat needs a desktop browser.
What AI is good and bad at in Roblox work
The tools differ in reach, but the models behind them share the same habits.
Usually good at
- Standard systems with a well-known shape: leaderstats, checkpoints, doors, tweens, a RemoteEvent round trip, a basic shop screen.
- Explaining an error message or a script line by line.
- Repetitive edits across many objects: renaming, setting a property on every lamp in a folder, adding the same behaviour to twenty parts.
- First drafts of UI layouts and greybox builds that you then adjust by hand.
Often bad at, so check these
- Trusting the client. A LocalScript that changes coins, or a RemoteEvent that takes the price from the player, looks fine and is easy to exploit. The server should decide anything that matters and check every RemoteEvent argument, as the RemoteEvents guide shows.
- Data that must not be lost. Saving code that skips
pcall, saves over a failed load, or ignores request limits can wipe progress. Compare it against the DataStore tutorial. - Your conventions. Unless the tool reads your place or you describe it, it invents names and duplicates systems you already have.
- Current APIs.
wait(),spawn()anddelay()are deprecated in favour oftask.wait,task.spawnandtask.delay, but models can still write them. Roblox's Code Assist docs warn of the same thing: suggestions may use older APIs. - Big jobs in one prompt. Long outputs get cut off, and later steps drift from earlier ones.
- Knowing whether the game is fun. Code that compiles can still be wrong, and even an agent that playtests cannot tell you whether a jump feels fair.
Most of these are easier to catch when you can read Luau yourself. How to script in Roblox Studio covers the basics: where scripts go, events, and reading Output.
A safe workflow for letting AI edit your place
Any tool that can change your place can also break it. This routine works the same with Assistant, an MCP client or a plugin agent.
- Save a checkpoint. Use File, Save to Roblox with Notes (Ctrl+Alt+S, or Cmd+Option+S on Mac) and note what you are about to try. If your scripts live in files through Script Sync or Rojo, commit to Git too.
- Clear prompts. "Add a sprint key" is reviewable; "make my game better" is not. For a whole game, ask for a playable core first, then add to it in rounds.
- Read every change. Check each script is the right type in the right place, that the server decides anything involving currency, damage or saving, and that nothing you did not ask for was deleted or renamed.
- Play-test it yourself. Press Play, try the awkward cases a player would, and keep the Output window open (from the Window menu). Paste any error line back with its script path and line number.
- Know your way back. Undo (Ctrl+Z, or Cmd+Z) takes back recent changes, including a plugin's when it records undo points. For a run that went badly wrong, open Window, Version History, click ⋮ next to your saved version, then Open Local Copy, and in that copy save over the place with File, Save to Roblox As.
- Keep secrets out. Never paste API keys, webhook URLs, cookies or passwords into a prompt, or let an AI hard-code them. Store them in the game's secrets store (Creator Dashboard, your game, Secrets) and read them on the server with
HttpService:GetSecret. Studio playtests cannot read that store: add test values under File, Experience Settings, Security, Local Secrets. - Test saving code on a copy. With Enable Studio Access to API Services on (File, Experience Settings, Security), Studio uses the live game's data stores, so Roblox advises doing it only in a separate test version.
How to prompt AI well for Luau
Most bad output comes from a prompt that left the model guessing. Roblox's own prompt guide opens with the same advice: be specific, and use instance names exactly as they are spelled.
- Name objects and where they live, as the Explorer shows them:
Workspace.Lobby.StartButton, not "the button". - Say what kind of script, where it goes, and which side decides: "a Script in ServerScriptService gives the coins; the LocalScript only asks".
- Point at what exists: "use the Coins value in the existing leaderstats, do not create a new folder".
- Ask for current Luau:
task.waitrather thanwait, and server-side checks on every RemoteEvent argument. - When fixing, paste the exact Output line, with the script path and line number, and say what you did just before it appeared.
- Ask how to test it. A good answer ends with the steps that prove it works.
| Vague | Specific |
|---|---|
| Make a shop. | Add a shop ScreenGui in StarterGui selling a Speed Coil for 100 Coins. A LocalScript fires a RemoteEvent named BuyItem in ReplicatedStorage with only the item name; a Script in ServerScriptService checks leaderstats.Coins, takes the coins and gives the tool. |
| Fix my script. | ServerScriptService.RoundManager errors on line 42 with "attempt to index nil with 'Humanoid'" when a player resets mid-round. Fix that case without changing how rounds start. |
| Make it night. | Add a Script in ServerScriptService that sets Lighting.ClockTime to 0 when the server starts. |
A prompt and its result
A good result is short and does exactly that. This one is written by us to show the pattern; any tool's wording will differ.
local Players = game:GetService("Players")
local lava = script.Parent :: BasePart
lava.Touched:Connect(function(hit: BasePart)
-- Only react to parts of a player's character, not NPCs or loose parts
local character = hit:FindFirstAncestorOfClass("Model")
if not character or not Players:GetPlayerFromCharacter(character) then
return
end
local humanoid = character:FindFirstChildOfClass("Humanoid")
if humanoid and humanoid.Health > 0 then
humanoid.Health = 0
end
end)
What to check before you trust it: it is a server Script, so the result is the same for every player; FindFirstAncestorOfClass("Model") finds the character even when the touching part is inside an accessory; and GetPlayerFromCharacter returns nil for NPCs, so they are ignored as asked. Then play-test: walk onto the lava, and drop an unanchored part on it to confirm nothing errors in Output.
Can AI make a whole Roblox game?
It can make a playable prototype of a simple game. It cannot, on its own, make a game people keep coming back to.
Roblox's own "Build your first game with Assistant" guide shows the realistic version: plan an obby with Assistant, let it build a greybox prototype, then play-test, report what is broken, and repeat until you can play from start to finish. It ends by encouraging you to treat Assistant as a collaborative partner rather than relying on it to build everything. Roblox also has Build, a separate mobile-first tool in the Roblox app that turns a description into a publishable game; its docs say it focuses on simpler 2D and 2.5D games for now and is rolling out gradually by region.
What AI does not do for you is the part that makes a game work: deciding what is fun, tuning difficulty and rewards, keeping the economy fair, running well on a cheap phone, and keeping player data safe. It gets you from an idea to something playable much faster, and writes a lot of the Luau on the way. You still decide what the game is, and you still test it.
For the practical version in Studio, the step-by-step way to make a Roblox game with AI using RoCode follows the same pattern: pick one core loop, ask for one system per prompt, review and undo what you do not want, and test after each one.
To build one by hand first, how to make a game in Roblox Studio goes from a Baseplate to a published coin course with two server scripts.
Common problems and fixes
Most AI trouble in Studio is a setup issue or a script in the wrong place. Keep the Output window open while you test: the error line names the script and the line.
The Assistant button is missing
Update Studio: an out-of-date copy shows an Update button in the upper-right corner. If the Assistant window seems to have vanished, look along the edges of Studio for it pinned as a tab. More fixes for a missing Assistant panel.
My MCP client does not see Roblox Studio
Restart both Studio and the client. For quick connect, install the client first, then restart Studio. If you configured it by hand, check the command path exists and the JSON is valid: one missing comma stops the file loading. The green indicator under Manage MCP Servers confirms a connection.
The AI says it added a script, but nothing happens in the game
Check the script's type and location. A LocalScript runs from places such as StarterPlayerScripts, StarterGui or the character, not from ServerScriptService. Also check whether the AI changed the place once in edit mode instead of writing a script that runs during play.
It works for me, but other players do not see it
A LocalScript made the change, so only your client sees it. Move it into a server Script, and if a button or key press triggers it, send a RemoteEvent and let the server decide.
The AI changed or deleted things I did not ask for
Undo the last changes, or restore the version you saved before you started. Next time, ask for one clear change and name what it must not touch, for example "do not change the RoundManager script".
Example: the play-test loop with RoCode
If you take the plugin-agent route, this is how the workflow above looks with RoCode: you press Play, and RoCode picks up from what you found. Say the first version of the lava script had a bug, so touching it did nothing and the Output showed an error.
I play-tested and touching LavaFloor does nothing. Check the Output and fix the lava script.
- Reads Studio's Output with Check Output, including the Server and Client lines from your last playtest, even after you press Stop
- Reads the lava script around the failing line with Read Script, then edits it with Edit Script
- Compile-checks the edited script with Check Script inside Studio. The check does not type-check, lint or run your code
- Sends the change as a batch that is one undo point in Studio's history
With plugin 3.9.11 or newer, RoCode can playtest your game in Studio and control a test character to check it works. It decides when to run a playtest, up to 2 per build plus 1 to check its own fix, and checks only what it chose to test, so press Play again and walk onto the lava to confirm the fix yourself. The prompt is an example written by us; the steps use the real tool names. How RoCode connects to Studio.
Questions
How do I get AI in Roblox Studio?
It is already there: update Studio and click Assistant on the right side of the mezzanine bar. Studio also has Code Assist, which suggests code as you type in the Script Editor. For a different AI, connect an MCP client such as Claude Code or Cursor, or install a plugin agent from the Creator Store.
How can I use AI in Roblox Studio for free?
Assistant comes with Studio and its docs list no price; their one stated cap is 50 procedural models per rolling 24 hours. Code Assist is built in with a daily cap. The MCP server is part of Studio, though your client may charge. RoCode's Starter plan is free with 1 credit a day, and many chat apps have a free tier. Every free tier is compared in free AI for Roblox Studio.
Is there an AI plugin for Roblox Studio?
Assistant is part of Studio rather than a plugin. Roblox also publishes an official plugin for AI assistants that connects Claude and ChatGPT to Studio's MCP server. Third-party agents exist too: RoCode works through a Studio plugin, and Ropilot and ForgeBlox (formerly Forge) work through their own desktop apps. See the Roblox AI tools comparison.
Can I use Claude or ChatGPT inside Roblox Studio?
Yes. Roblox's official agent plugin connects Claude Code, Cowork in the Claude desktop app, the ChatGPT desktop app and the Codex CLI to Studio's MCP server, and other MCP clients such as Claude Desktop or Cursor connect through quick connect or a configuration. You can also add your own Anthropic, OpenAI or Google API key to Assistant under Manage API Keys. Either way, that company's plans and prices apply, not Roblox's.
Which AI is best for Roblox scripting?
It depends on the job more than the model. For one script in the place you have open, Assistant is built in and needs no setup. To use Claude, ChatGPT or Cursor, connect them through Studio's MCP server. A plugin agent edits your place from its own chat. Which tool for which job matches common tasks to a route.
Can AI see my whole Roblox game?
Assistant, an MCP client and a plugin agent work on the place you have open in Studio rather than on text you paste. Studio's MCP server, for example, lets a client explore the Explorer tree and read scripts. A chatbot in a browser tab sees only what you paste, which is why it guesses names and paths.
Is it safe to let AI edit my Roblox game?
Yes, with a routine: save a version first, ask for one clear change at a time, read every change, and play-test it yourself. Check that the server decides currency, damage and saving, and never paste API keys or passwords into a prompt. The safe workflow has the steps.
Do I still need to learn Luau if I use AI?
Enough to read what it writes: to spot a script in the wrong place, a missing server check, or a save that can lose data. The client and server guide and the script errors guide cover what matters most.
Sources and further reading
- Roblox Creator Docs: Assistant for Studio. abilities, chats and branching, Planning Mode, slash commands, segmentation in early preview, the procedural model limit (checked 22 October 2026)
- Roblox Creator Docs: Assistant prompt guide and examples. being specific, edit time versus run time
- Roblox Developer Forum: Studio MCP Server Updates and External LLM Support for Assistant. using your own API key in Assistant
- Roblox Creator Docs: Assistant skills
- Roblox Creator Docs: Connect to the Roblox Studio MCP server. setup, quick connect clients, tools, troubleshooting (checked 22 October 2026)
- Roblox on GitHub: roblox-studio-agent-plugin. Roblox's official plugin for AI assistants: supported apps, what it runs, MIT licence (README read 22 October 2026)
- Roblox Creator Docs: Build with a coding harness. Script Sync, MCP and Git
- Roblox Creator Docs: AI on Roblox
- Roblox Creator Docs: Build your first game with Assistant. /generate_material, and Continue after the maximum output length
- Roblox Creator Docs: Create games with Build. 2D and 2.5D games, ages 9 and older, rolling out by region (checked 22 October 2026)
- Roblox Creator Docs: Script Editor, Code Assist
- Roblox Creator Docs: Version History
- Roblox Creator Docs: Secrets stores
- Roblox Creator Docs: Data stores. Studio access to API services
- Roblox Engine API: Roblox globals. wait, spawn and delay deprecated
How the code was checked: every script on this page passes Luau's strict type checker against Roblox's API definitions (luau-lsp, 30 October 2026). A type check catches misspelt APIs and wrong types, not game logic, so playtest in Studio before you publish.