Get started with Roqer.
Roqer works on the place you already have open in Roblox Studio. It runs on your computer, needs no account, and uses a model you connect; the conversation goes from your machine straight to that provider.
Set up
- Install Roqer from the download page and open it.
- Let Roqer install its Studio plugin, which it does every time it starts, then fully close and reopen Studio once. Studio does not load a plugin in place, and a half-loaded one fails in ways that look like the agent misbehaving.
- Open your place in Studio, signed in to the account that owns it.
- Connect a model under Settings → Models. Install the Codex app for a ChatGPT subscription or Claude Code for a Claude subscription, and sign in from Roqer. Or, under Your endpoints, add an API key for an OpenAI- or Anthropic-compatible service, or the address of a model server on your computer.
Roqer shows the place as connected once Studio comes back. Choose a model in the composer and describe what you want built.
Approval modes
Chosen in the composer, before a run starts.
| Mode | What it allows |
|---|---|
| Ask first | Confirm every change before it reaches your place. |
| Auto approve | Ordinary, recoverable edits run on their own. Anything that cannot be undone still asks. |
| Full auto | Nothing asks: publishing, asset spend, and arbitrary Luau all run unattended. This is the default, and you can change it in the composer at any time. |
| Read only | Inspect the place and block every change to it. |
An irreversible action — publishing, spending on assets, deleting broad project data, changing credentials — always stops for an explicit confirmation, and Full auto is the single exception, because choosing it is that confirmation for the whole run.
What a run can do
- Inspect the hierarchy, scripts, properties, selection, and connected Studio sessions.
- Change scripts and instances with revision-aware edits that are read back after they are written. An edit to a script that changed since the agent read it is refused rather than overwriting your work.
- Playtest solo or with several clients, drive input and UI, and simulate devices and networks.
- Diagnose with logs, screenshots, script and micro-profiler recordings, memory and scene-cost analysis.
- Model in Blender when you turn it on under Settings → Blender: the agent writes the model, checks a preview render, and uploads it into your place.
- Use the Creator Store to search, preview, and insert assets, and upload your own with a Roblox Open Cloud key set under Settings → Roblox.
What a run reports
A run ends with what its evidence supports, not with what the model believes. If a script write was not read back at the revision it reported, a collected check failed, a task needed runtime evidence and none was recognized, a task was left open, or any step failed, the run cannot report a clean result — whatever the closing message says. That is the difference between a finished run and a proven one, and Roqer never blurs it.
Good to know
- One run is active at a time.
- Keep the place open in Studio while a run is working.
- Your chats, diffs, evidence, and run history stay on your machine.
- Keep your own version control and backups. A model can still be wrong, and
Full autoruns unattended.