Editor workflow
Advanced setup for developers
Bricklayer stores each game as a plain local Luau project, so you can bring your own editor, version control, and build tools.
New to Roblox development?
Skip this page and use the first-game guide instead.
How the project is laid out
When you open or create a game, Bricklayer writes a normal project folder to your computer and connects a plugin inside Roblox Studio. Studio stays your place editor; the folder holds the scripts. Anything that edits files on disk (an editor, a formatter, Git, or a coding agent) works against that folder, and the plugin keeps it in sync with the open place.
Bring your own tools
Add only what your workflow needs.
| Tool | What it’s for | Notes |
|---|---|---|
| VS Code & CLI | Edit the local project directly and run commands against it. | Open the project folder in any editor. Bricklayer keeps files in sync while you work; no proprietary format is required. |
| Node | Run project scripts and JS-based tooling. | Use your own Node toolchain for build steps, linters, and codegen. Install dependencies with npm install and run scripts with npm run <script>. |
| MCP | Connect a compatible coding agent to the project. | Point an MCP-capable agent at Bricklayer’s project tools so it can read and edit the same local files the editor manages. |
| Rojo | Map local files into Roblox Studio. | Serve your project with rojo serve and connect from the Rojo Studio plugin (default port 34872). Use your existing default.project.json. |
| Git | Version control and rollback. | The local project is an ordinary folder, so git init, git status, and git restore all work. Review AI changes as diffs and revert anything you do not want. |
| Luau | Author and format game scripts. | Edit .luau files with your own language server and formatter. Bricklayer syncs them into Studio as you save. |
Working alongside the AI
AI edits land as file changes in the same project, shown as a before-and-after diff you approve before they apply. Because it’s all on disk, you can review those changes in Git, keep your own commit history, and roll back a change from either Bricklayer or the command line.
Playtest every milestone in Roblox Studio. No toolchain replaces running the game.