How Bricklayer works with Roblox Studio
What Bricklayer does, what Studio still does, and how your scripts move between them.
Updated November 8, 2026
Bricklayer is a desktop editor that sits next to Roblox Studio and lets an AI work on your game safely. It does not replace Studio.
Who does what
| Bricklayer Editor | Roblox Studio | |
|---|---|---|
| Where your scripts are edited | Yes, as real .luau files | Yes, they stay in sync |
| Building the place (parts, terrain, lighting) | Your AI can help through Studio | Yes, this is still home |
| Pressing Play | Can ask Studio to start a playtest | Yes |
| Talking to an AI | Yes | |
| Publishing to Roblox | Never | Yes, when you choose to |
The three pieces
- The local project. A normal folder on your computer that holds your game's scripts. Because it is just a folder, any tool that edits files can work on it, including Git if you want history.
- The Bricklayer plugin in Studio. Bricklayer installs it for you. It keeps the open place and the local project in sync over a connection on your own computer.
- Your AI. Claude Code, Codex, Gemini, or Bricklayer chat through OpenRouter. It reads and edits the local project, and every file change shows up as a diff you approve.
Where your work lives
Your game stays on your computer and in Studio. The connection between Bricklayer and Studio is entirely local: the plugin talks to Bricklayer on your own machine, not to the internet.
The only outside service involved in building is the AI provider you choose, because it needs to read the parts of your project it is working on. See What Bricklayer sends, and where.
What you stay in control of
- You confirm which game Bricklayer works on before anything is copied.
- Every AI file change waits for your approval.
- Studio changes are undoable.
- Nothing is published unless you publish it yourself.
Did this answer your question?
Related articles
Still need help? or start a thread in the community forum.