News
What's new in AI Roblox development
May 2, 2026 · Updated July 25, 2026
A lot has shipped since the Studio MCP server stabilized in March. Roblox announced an agentic direction for Studio, shipped Planning Mode and a Playtesting Agent, added Procedural Models, and made it one click to wire external tools into Studio's MCP. The OpenGameEval benchmark also more than doubled in size, and several new models landed on the leaderboard. Here's what changed and what it means for your workflow.
Studio is going agentic
On April 15, Roblox SVP of Engineering Nick Tornow announced that the Assistant is moving from a single-prompt tool to an autonomous development partner that plans, builds, and tests - the same loop a human developer follows. According to Roblox, 44% of the top 1,000 creators already use Roblox Assistant or third-party AI tools via MCP.
The agentic direction has three pillars.
1. Plan: Planning Mode
Announced May 1, Planning Mode changes how Assistant handles a request. Instead of acting immediately, it analyzes your code and data model, asks clarifying questions, and produces an editable action plan. You review, modify, or reorder steps before any change happens. Each session creates checkpoints you can revert to.
The plan acts as a small design document that the agent uses to execute. It integrates with three generation tools - Material Generation, Mesh Generation, and Creator Store imports - and a verification step that playtests the result, reads logs, captures screenshots, and feeds bugs back for automatic fixes.
Coming next: multi-agent execution where separate agents handle scripting, layout, and UI concurrently, plus a node graph for visualizing and editing the plan-build-test workflow.
2. Build: Procedural Models with AI generation
Procedural Models (entered edit-time beta April 30 and reached full release May 18) are a new Instance type that rebuilds its contents when parameters change. Assign a Generator Module written in Luau, define attributes that trigger regeneration, and the model updates on edit. Change the Size and a bookcase adds shelves; switch a Material attribute from wood to stone and every surface updates.
You can generate them through the Assistant (/generate_procedural_model a medieval castle with terracotta roofs) or through the MCP server's generate_procedural_model function. The Assistant picks attributes from your prompt and produces models built from primitive parts you can keep editing. They can be published to the Creator Store with automatic sandboxing that blocks access to sensitive APIs.
The interesting part is reusability: instead of a one-off model, you get a parameterized asset that can be adjusted, shared, and composed with other Procedural Models.
3. Test: Playtesting Agent
The Playtesting Agent (beta) acts as an automated tester. It runs your game against the original plan, reads output logs, simulates keyboard and mouse input, and verifies behavior on its own. Bugs it surfaces feed back into the next round of planning, closing the loop.
First teased on March 6 as MCP-powered playtest automation, it's now wired into Planning Mode's verification step. You no longer need to manually playtest after every iteration.
Data Model Search Subagent: smarter exploration
Shipped April 28, this addresses a real problem with large projects: as tool calls pile up in the conversation, the agent has less room to reason. The Data Model Search Subagent runs on its own thread to explore the project, then returns a compact summary. Multiple subagents can run concurrently, investigating different parts of the codebase in parallel.
For a 50,000-line game with hundreds of instances, this is the difference between an agent that loses the plot and one that doesn't.
MCP Quick Connect: one-click setup for external tools
Also shipped April 28, Quick Connect detects supported MCP clients on your machine - Claude Code, Claude Desktop, Cursor, Gemini CLI, VS Code, Codex CLI, and Antigravity - and adds them to Studio with a single toggle. No JSON editing, no config file hunting. The manual setup option is still there for clients that aren't auto-detected.
Combined with the new Copy Unique ID feature (right-click any instance for a stable text handle to paste into external prompts), it makes moving between Studio and tools like BloxBot, Claude Code, or Cursor a lot smoother.
OpenGameEval: from 47 to 117 evaluations
Roblox's OpenGameEval benchmark has expanded twice:
- Debug evals (March 3): 30 evaluations testing bug-fixing ability. Each one introduces a bug - renamed instances, inverted logic, changed constants, state management issues - and asks the model to find and fix it. The current leader is Claude Fable 5 (64.7%), followed by Gemini 3.1 Pro (56.7%) and GLM 5 (56.0%).
- Code Generation Batch 2 (April 14): 40 evaluations with higher complexity and broader place coverage, including from-scratch baseplate scenarios that require multi-step system creation. Claude Fable 5 now leads this harder set (50.34%), while Claude Opus 4.6 has the lowest tool error rate (0.71%).
The benchmark now covers 117 evaluations across two skill categories. Roblox currently publishes seven models on the 87-eval code-generation board and eleven on the 30-eval debug board. See the full current leaderboard breakdown.
New models since March
| Model | Pass@1 | Pass@5 | Tool err | Notable |
|---|---|---|---|---|
| Claude Fable 5 | 50.34% | 62.07% | 1.40% | Leads Pass@1 and consistency |
| Claude Opus 4.6 | 48.05% | 59.77% | 0.71% | Lowest tool error rate |
| Gemini 3.5 Flash | 48.05% | 63.22% | 3.30% | Leads Pass@5 |
| Gemini 3 Flash Preview | 47.82% | 60.92% | 5.51% | Current 87-eval result |
| Claude Opus 4.7 | 43.45% | 58.62% | 1.33% | 39% fewer calls than 4.6 |
| GPT-5.5 (Reasoning: M) | 40.69% | 56.32% | 0.91% | Current 87-eval result |
| GPT-5.4 (Reasoning: M) | 40.23% | 55.17% | 1.81% | Current 87-eval result |
Claude Opus 4.7: the efficiency play
Opus 4.7's Pass@1 (43.45%) looks like a regression from 4.6 (48.05%), but the headline number misses the point. On the expanded 87-eval set, the gap between 4.6 and 4.7 isn't statistically significant (p=0.24). Where 4.7 stands out is efficiency: 39% fewer tool calls per task, with the largest drops in exploration tools like search_game_tree, script_grep, and inspect_instance. For practical use that means faster sessions and lower costs, especially on large projects.
Claude Fable 5: the current leader
Fable 5 leads the published 87-eval code-generation board at 50.34% Pass@1 and the debug board at 64.67%. The detailed Roblox review shows its clearest gains on bounded tasks with a named target and specific expected behavior. Gemini 3.1 Pro remains second on Debug (56.67%) but has not been evaluated on the expanded code-generation set.
What this means for your workflow
- Use Planning Mode for complex features. The Plan → Build → Test loop with checkpoints and verification beats ad-hoc prompting on multi-step tasks. It's built into Roblox Assistant now, and the pattern translates to any AI tool you already use.
- Don't commit to one model. The benchmarks make it clear no model wins everywhere. Match the model to the task: Fable 5 for bounded building and debugging, Opus 4.6 when tool-call precision matters, Gemini 3.5 Flash for iterative work, and Opus 4.7 when tool-call efficiency matters.
- Try Procedural Models. Parameterized, reusable AI-generated assets are a new primitive. Even if you write your own Generator Modules, the pattern is worth understanding.
- Wire up MCP Quick Connect. If you use Claude Code, Cursor, or another supported client, the one-toggle setup removes the last bit of friction from connecting external AI tools to Studio.