Use VS Code, Git, Rojo, or your own tools with Bricklayer
Your project is a plain folder of Luau files, so your favourite editor, version control, and build tools all work on it.
Updated November 8, 2026
You do not need any of this to use Bricklayer. But if you already have a workflow, Bricklayer fits into it rather than replacing it.
Why it works
When you open or create a game, Bricklayer writes a normal project folder of .luau files and connects a plugin in Roblox Studio. Studio stays your place editor; the folder holds the scripts. Anything that edits files on disk works against that folder, and the plugin keeps it in sync with the open place.
Common setups
| Tool | How it fits |
|---|---|
| VS Code or any editor | Open the project folder and edit. Bricklayer syncs your saves into Studio. |
| Git | git init in the project folder. Review AI changes as diffs, commit what works, and git restore what does not. |
| Rojo | Serve your project with rojo serve and connect from the Rojo Studio plugin (default port 34872), using your existing default.project.json. |
| Luau tooling | Use your own language server and formatter on the .luau files. |
| Node | Run your own build steps, linters, and codegen with npm run. |
AI changes and your history
AI edits land as file changes in the same folder, shown as a diff you approve. Because it is all on disk, you can review them in Git and roll back from either Bricklayer or the command line.
Playtest every milestone in Roblox Studio. No toolchain replaces running the game.
Full details: Advanced setup for developers.
Did this answer your question?
Related articles
Still need help? or start a thread in the community forum.