Everything Potato AI does, inside Studio.
Nine capabilities, one boundary: your open Roblox place. This page goes deep — for the overview, see the homepage.
1. Connect your open Studio place
Use the Potato AI Windows app with Roblox Studio and the Potato plugin. Sign in, link Roblox and choose the Studio place to edit. The website manages your account and projects; builds start in the desktop app.
If several Studio windows are open, choose the place you want to edit. Continue Build requires the original saved experience and place.
- Desktop sign-in required for builds
- Choose the Studio place to edit
- Revoke paired devices from Settings
2. Plan first, then build
Large requests start with inspection, not edits. Potato AI reads the relevant game tree and scripts, then shows a step-by-step plan: systems, scripts, UI, remotes, playtest, fixes.
If your request is genuinely ambiguous, it asks one grouped question up front instead of five interruptions later. Plans that touch important existing systems pause for Accept / Reject before anything runs.
- Game-tree inspection before changes
- Duplicate-system checks (no second CoinService)
- Destructive steps flagged in the plan itself
3. Builds that run while you watch — or walk away
Builds run on background workers with saved progress and checkpoints. Reopening the desktop app shows the saved run. A paused build resumes only after you press Continue Build and the server verifies usage, Studio and the original place.
Every tool call travels the same path: model → permission gateway (auth, project scope, confirmation policy, audit) → Bridge → Studio. The model can only use the 20 allowlisted Studio tools.
- Refresh-safe live progress
- Max 60 model steps / 80 tool calls per run
- Every action audit-logged with its run
4. Playtested, not just written
After building, Potato AI starts a real Studio playtest: spawning, opening the shop UI, firing remotes, and reading console output. Viewport captures verify layout and scale where it matters.
Errors trigger up to five automatic repair cycles — patch, retest, verify. If something still fails, you get the actual error and what was tried, not a green checkmark.
- Real playtest sessions in your place
- Console-driven repair loop (max 5 cycles)
- No success claimed without verification
5. Memory that compounds
Potato AI remembers what matters per project: where systems live, which framework you use, the rules you set (“mobile-first UI”, “don't touch combat”). Older conversation turns compress into summaries so long projects stay coherent.
You can also write explicit build preferences from the sidebar Memory panel — stored against your project, loaded into every future build.
- Per-project preferences you can edit
- Automatic architecture summaries
- “Make the shop bigger” just works
6. Confirmations where they count
Safe work flows: new scripts, new instances, small fixes to Potato-created code. Sensitive work pauses: replacing large existing scripts, big deletes, architecture changes, any Creator Store insert.
Each confirmation shows the reason, the target, and a before/after summary. Reject, and Potato AI finds another way.
- Risk engine, not vibes — 5 enforced levels
- Overwrites of 50+ lines always gated
- External assets never auto-inserted
7. Undo without drama
Every build records its change-sets: previous script sources, old property values, created-object paths, and safe in-Studio backups for destructive replacements. Revert a change-set from the project inspector.
One rule, stated everywhere: undo reverts the Roblox changes. AI work already done still counts toward usage.
- Per change-set reversal
- Backups kept out of gameplay
- Irreversible steps disclosed before they run
8. Models it generates itself
Shops, maps, and props are generated from primitives, MeshParts, materials, and procedural generation — no dependency on the asset store. When generation can't cover a need, Potato AI may propose a Creator Store model with its creator, ID, and reasoning.
Approved third-party models are inserted, then inspected: unexpected requires, obfuscated code, and stray network behavior get flagged before anything runs.
- mesh / material / procedural generation
- Approval-first external assets
- Inserted scripts inspected, not trusted
9. Research when it matters
Unsure about an API? Potato AI checks the official Roblox documentation first through its docs tools, then your project context — and only then a narrow web search for Roblox development specifics.
No background browsing, no executables, no unrelated topics. Research serves the active build or it doesn't happen.
- Official docs before blogs
- Deprecation checks before use
- Scoped to the current build