RoCode documentation

What RoCode is

RoCode (RoCode.app) is an AI coding agent for Roblox Studio. You describe a feature in a web chat at rocode.app. A free RoCode plugin from the Roblox Creator Store then carries out the agent's steps in the place you have open: it reads the objects and scripts a step needs, writes the Luau, creates or edits Scripts, LocalScripts, ModuleScripts and other instances, and compile-checks its scripts inside Studio before it finishes.

DeepSeek V4 Flash, GPT-OSS 120B, GLM 5.3, Claude Sonnet 5.5, Claude Opus 5.5 and GPT-6 Astra are third-party models that RoCode runs through OpenRouter with its own instructions and Studio tools. RoCode has no models of its own. See Models and credits for which plan includes which model.

Each message runs in one of two modes, picked in the composer: Build, which makes changes in Studio, or Ask, which answers questions about your game without changing anything. See Build and Ask modes.

Requirements

Not needed: a desktop app, a command line, config files, an MCP server or your Roblox password. RoCode never asks for your Roblox password.

Install the plugin and pair it with the chat

Install and connect, step by step

1. Create a free account. Sign in at rocode.app with an email code, Google, Roblox or Discord. See Sign-in options.
2. Install the plugin. Open the RoCode plugin on the Creator Store and install it. Installed plugins appear in Studio's Plugins tab. In Studio's plugin manager, RoCode is listed as RoCode AI.
3. Allow the permissions. When Studio asks, allow HTTP requests to www.rocode.app and relay.rocode.app, and Script Injection. The table below says why.
4. Open a place in Roblox Studio: a game you are working on, or a new Baseplate. The RoCode panel shows a pairing code.
5. Pair the chat. Open rocode.app/chat in a desktop browser. In the Roblox Studio isn't connected card, type the code and press Connect.
6. Confirm in Studio. The RoCode panel shows a confirm row with your account. Press Connect there. It waits up to 2 minutes, then shows a new code.

Sign-in options

The Studio permissions the plugin asks for

One Studio setting is optional and stays your job: Enable Studio Access to API Services. You need it to test data store saving in Studio, and RoCode cannot change it for you. In Studio, open File > Experience Settings > Security, turn it on and click Save. The place has to be published first. Studio then uses the same data stores as the live game, so Roblox recommends turning this on only in a separate test copy.

How pairing works

Your first run

The chat will not send a message until a Studio is connected: the send button stays off, and hovering over it shows Connect the plugin first. Once Studio is connected, describe one change.

Write a good first prompt

• One feature at a time. It works better than a whole game in one message.
• Say what should happen, in plain words. You do not need class names or to know where scripts go.
• Point at what matters. Type / in the message box to attach an exact Studio object path, such as the script you want changed. With the + button you can also attach up to 12 text files (20,000 characters in total) and, on Claude Sonnet 5.5, Claude Opus 5.5 or GPT-6 Astra, up to 4 images per message.
• Just a question? Switch the composer to Ask and nothing in your place changes.
• Or dictate it. The mic button records your prompt; the transcript lands in the message box for you to edit and send.

An example prompt written by us. The tool names are real, but what a run does depends on your place. RoCode does not start playtests: press Play in Studio to try the result.

Where RoCode puts things

Scripts use game:GetService(), and properties are set as Studio's own types, such as Color3, Vector3, UDim2, CFrame and Enum values.

What you see while it works

• A step-by-step log. The chat lists each step by the tool labels in the tools table. Every read and every deletion shows with its path.
• How long it takes. It depends on the task, the size of your place and the model. One run can last up to 80 model turns or 5 hours. The chat shows the credits a run is using while it works.
• Your next prompt can wait in line. While a run is working, you can queue the next prompt. You can have up to 3 runs going at once.
• No edits during a playtest. If a playtest is running when a change is due, RoCode stops the test first, or asks you to press Stop.

Stop and Continue

Stop a run whenever you like. If a run stops partway, from an error or a usage limit, the changes made so far stay, and Continue picks up where it stopped. A failed run that already changed your place offers Continue instead of starting the prompt again. Runs that you stop count up to where they stopped. When a run fails because of a problem on our side, its credits go back to your balance automatically.

Chat settings

Build and Ask modes

Every message runs in one of two modes. Build is the default and changes your place. Ask, added on 9 October 2026, answers questions about your game and changes nothing.

Switch modes in the composer

1. Look at the toolbar under the message box. On the left are the + button for attachments, the mode chip and the plugin status. On the right are the model picker, the mic and Send.
2. Click the mode chip. It shows the mode you are in, Build unless you changed it.
3. Pick Ask (Answers questions about your game without changing anything) or Build (Makes changes in Studio).
4. Type your message. In Ask mode the box reads Ask anything about your game..., and your message is tagged Ask in the chat.

The choice is remembered in that browser, so a chat you open later starts in the mode you last picked. Check the chip before you send a change.

An example prompt written by us, in Ask mode. The tool names are real, but what a run reads depends on your place.

What Ask can read

An Ask run may use these 9 tools, all of which only read: List Children, Get Descendants, Find Child, Search Game, Search Scripts, Get Properties, Read Script, Check Output and Check Script. Check Script only compiles a script; it never runs it.

Good to know about Ask

• It still needs a connected Studio. Ask reads your place, so the chat will not send until the plugin is connected.
• Ask runs are short. They are made for an answer, not a long job. Ask a follow-up if you want more detail.
• From answer to change. When Ask suggests a fix, switch the chip to Build and ask for the change.
• A prompt keeps its mode. A queued, retried or continued prompt runs in the mode it was sent in, even if you switch the chip afterwards.

The 24 tools

The agent works through 24 tools in the plugin, and every plan gets all 24. In Build mode it can use any of them; in Ask mode only the 9 that read. This is each one by the label the chat shows, grouped by area.

You may also see Agent Selection in the log. It is the agent's internal list of paths, used before Group Selection, and it is never Studio's own selection. It is not one of the 24.

The 12 ready-made structures

Place Prefab builds these from parts: no meshes. Anything else is built part by part with Build Structure.

1. Wall
2. Floor slab
3. Roof wedge
4. Room
5. House shell
6. Tower
7. Platform
8. Bridge
9. Staircase
10. Fence segment
11. Arena
12. Obstacle course

The 6 UI layouts

Build UI starts a ScreenGui from a shop, inventory, HUD, dialog, leaderboard or settings layout, or a blank panel. Layouts come with placeholder items. The companion LocalScript adds hover effects and makes the Close button hide the screen; the game logic is written as separate scripts. RoCode can also build a ScreenGui object by object, with Frames, TextButtons, TextLabels, ScrollingFrames and UICorner.

Checks, Output and undo

What Check Script checks

Check Script runs a script through Luau's compiler inside Studio. A compile error comes back with its line and column. It also warns about the patterns below. It doesn't type-check, lint or run your code, so it catches compile errors and a few risky patterns, not logic bugs.

After every Create Script or Edit Script, the agent is told to run Check Script on that script before it finishes. If a check fails, RoCode can't finish the run until a later check passes. After two tries it can finish, and it tells you what is still failing.

Errors from your playtests

RoCode reads Studio's Output only when a step asks for it, usually with Check Output. It does not watch the Output window, and the runtime lines it can read come only from playtests you run. The flow:

1. Press Play in Studio and reproduce the problem.
2. Tell RoCode what broke. You can press Stop first: Server and Client lines from your last playtest are kept.
3. Check Output reads the Output, then RoCode reads the script around the error line and edits it.
4. Play again to confirm the fix.

Undo, batch by batch

RoCode sends its changes to Studio in batches, and each batch is marked as an undo point in Studio's history. Undoing a longer run takes several presses of Ctrl+Z (⌘Z on Mac). The chat's Revert button only rewinds the conversation, not Studio.

Deletions

Since 9 October 2026, RoCode deletes or ungroups an object only when one of these is true:

• RoCode created that object earlier in the same chat.
• Your message asks it to remove the object: by name, by saying everything, or while you have it selected in Studio.
• RoCode asked whether to delete it, and you said yes.

Otherwise the delete is refused and RoCode asks you. Each deletion shows in the chat with its path and is part of that batch's undo point in Studio, so you can undo it batch by batch. In Ask mode, Delete Instance is refused.

The header line in new scripts

Scripts made with Create Script, and scripts rewritten whole, start with the comment -- Generated by RoCode AI | https://rocode.app. Targeted edits don't add it.

Models and credits

Max includes every model. Starter users pick DeepSeek V4 Flash or GPT-OSS 120B.

The model picker sits on the right of the composer toolbar, under the message box. It shows every model. A model your plan does not include has a lock and the name of the plan it needs.

Images in a message need Claude Sonnet 5.5, Claude Opus 5.5 or GPT-6 Astra: PNG, JPG or WebP, under 10 MB each, up to 4 per message.

If a paid model is slow to start, RoCode first tries the same model through another provider. If GLM 5.3 still fails, DeepSeek V4 Flash can finish a text task, charged at its lower price, and the line under the reply says so. On other models the run stops, and a run that fails on our side gets its credits back. Runs on your own key never switch.

The first time you pick Claude Sonnet 5.5, Claude Opus 5.5 or GPT-6 Astra, RoCode shows what it costs and asks you to confirm. If you are under 18, a parent or guardian needs to agree. Long chats cost more on these three models, so start a new chat for a new task.

What a credit is

A credit measures what a run costs to compute. Stronger models and longer runs use more. The chat shows the credits a run is using while it works and the total under every reply.

For scale, at current rates: an advanced task (GLM 5.3, the default on paid plans) uses about 4 credits, and a standard task (DeepSeek V4 Flash) about 0.4. That makes Pro about 35 advanced tasks a month or 375 standard tasks, Studio about 100 or 1,000, Ultra about 225 or 2,250 and Max about 500 or 5,000. Long tasks use more. Claude Sonnet 5.5, Claude Opus 5.5 and GPT-6 Astra use credits faster. On the free models, 3 credits is enough for a few small tasks a day.

Every plan, paid ones included, gets 3 free credits a day on DeepSeek V4 Flash and GPT-OSS 120B. On a paid plan, your plan credits are used after those.

Your balance is at the top of the chat. On a paid plan it reads like 118.4 credits. On Starter it reads like 2.4 of 3 today. Click it to see your plan credits and when they reset, your pack credits, and the free credits left today. The line under each reply shows what the run used, the model that ran, the number of steps and the time. The Usage section of your account page shows your balance, the reset date, the last 14 days and every run with its credits, and you can download it as a CSV file. Voice input uses a small amount of credits.

If you stop a run, it counts up to where it stopped. A run that fails because of a problem on RoCode's side gets its credits back automatically. One run also pauses after a set number of credits and asks before it goes on; see Limits.

When credits reset

Your own OpenRouter key (paid plans only)

• Plans: every paid plan. It is not available on Starter.
• Where: the last card in the chat's model picker, tagged OpenRouter. You add an OpenRouter API key (sk-or-v1-...) and a model ID.
• Billing: OpenRouter bills your account, and no RoCode credits are used, even after your monthly credits run out.
• Subscriptions: none needed. Claude, Claude Code and ChatGPT subscriptions can't be connected.
• Checked: the key, with OpenRouter, when you save. The model is not checked, so try yours on a small task first.
• Stored: encrypted, and you can remove it any time. See Privacy and security.

Credit packs

On paid plans you can buy extra credits on the account page: from 25 credits for $2.99 up to 1,500 credits for $94.99. Packs are used after the monthly credits, and they never expire. If your plan ends, they stay on your account and work again when you pick a plan. Packs are not sold on Starter.

Limits

What RoCode does not do today

• Press Play or run playtests on its own
• Move a character, click buttons or simulate input
• Take screenshots of your game. You can attach your own screenshot when you use Claude Sonnet 5.5, Claude Opus 5.5 or GPT-6 Astra.
• Generate meshes or animations
• Sculpt or paint terrain
• Insert models from the Toolbox or Creator Store
• Publish or save your place, or change Experience Settings
• Build a finished, balanced game from one sentence
• Work on a phone: the chat shows that it is a desktop app only

It also has no tools for game passes, developer products, uploading assets or turning on API Services, and it does not run your scripts. It writes Luau that uses DataStoreService, RemoteEvents, TweenService or PathfindingService like any Roblox script, and builds the instances those scripts need, but you playtest to confirm they work.

Privacy and security

This is how RoCode works today, in the same words as the homepage. The Privacy Policy is the full policy, and the Terms cover using RoCode.

RoCode's instructions also tell the agent to treat text inside your place as data, not instructions, and to refuse exploits, backdoors and scripts meant to harm players or steal data.

Troubleshooting

Most setup problems are one of the cases below. If yours is not, ask in the RoCode Discord, which is where support happens.

Plans

• Every plan gets all 24 tools. Paid plans add more models, your own OpenRouter key, credit packs and no daily cap, and their runs go ahead of Starter runs in the queue.
• Annual plans cost 30% less than 12 months of the monthly plan, are billed once a year and get the same credits, refilled every 30 days. An annual plan bought before credits stays as it is.
• Paddle runs checkout as the merchant of record: it takes the payment, handles sales tax or VAT, issues the invoice and is the seller on your receipt. RoCode does not store card details.
• If you are under 18, ask the cardholder before you buy.
• Cancel from your account page. You keep your plan to the end of the paid period and aren't charged again.

Upgrades, downgrades and the full comparison are on the pricing page.

Refunds

• Refunds are in full within 14 days of any payment, including renewals and credit packs. That applies for any reason, wherever you live.
• How to ask: at paddle.net, or by replying to your Paddle receipt.
• After a refund, new plans, upgrades and credit packs are paused for 60 days. The credits that payment bought are removed.
• After 14 days: payments are not refundable, except where the law requires.

Support questions

Sources and further reading

• RoCode Plugin on the Roblox Creator Store. the plugin this page describes
• Pricing. every plan, credit packs, changing plans and refunds
• Privacy Policy. the full privacy policy
• Terms of Service. the terms for using RoCode
• Changelog. every release, newest first, including the one-time pairing code on 27 September 2026
• Roblox Creator Docs: Creator Store. installing a plugin from the Creator Store
• Roblox Creator Docs: Data stores. turning on Studio access to API Services, and why to use a test copy
• Roblox Creator Docs: Output. the Output window that Check Output reads
• Roblox Creator Docs: Script Editor. where the Script Analysis window lists errors in a script