Help & FAQ

Setup & diagnostics

Most setup failures come from one of four places: the project, the Studio plugin connection, file sync, or your AI provider.

Start with the built-in check, then use the tables below to map a symptom to a fix.

Run the built-in troubleshooter first

Open Troubleshoot (Setup & Diagnostics) from the command palette in Bricklayer Editor, or click Open the troubleshooter on the Welcome screen. It checks every part of the chain (trust, project, live-sync runtime, plugin, Studio, connection, tools, and your AI agent), floats problems to the top, and gives you a one-click fix or a copyable command beside anything that’s red. No terminal required.

Work from the top item down, since later checks depend on earlier ones passing, then hit Re-run checks.

What the diagnostic checks

CheckWhat it verifiesIf it fails
ProjectA valid local project exists and its files are readable.Reopen the game from the welcome screen so Bricklayer can recreate the project.
Studio pluginRoblox Studio is running and the Bricklayer plugin has an open connection.Start Studio with the project open, then re-run the check.
SyncFile changes move between the local project and Studio.Confirm the correct game is open; a mismatched place blocks sync.
AI providerThe selected agent (Claude Code, Codex, Gemini) or OpenRouter chat is reachable and authorized.Re-enter the API key or sign in again for the provider you chose.

Common issues

Plugin shows “disconnected” in Studio

Cause. Studio was opened after Bricklayer, or the plugin toolbar was never activated.

Fix. Keep Studio open with the project loaded, activate the Bricklayer plugin from the toolbar, then re-run the check.

Diagnostics cannot find Roblox Studio

Cause. Studio is closed, or a different place is open than the one Bricklayer expects.

Fix. Open the exact game Bricklayer created or connected. The place name in Studio must match the one shown in Bricklayer.

File changes do not appear in Studio

Cause. Sync is paused, or edits were made to a place that is not the connected project.

Fix. Save in Studio, verify the connected game, and re-run the check. Sync only targets the confirmed project.

AI will not respond or returns an error

Cause. Missing or expired API key, or the selected model is unavailable.

Fix. Re-enter the provider key. On OpenRouter, pick a currently available model. Free endpoints go offline without notice.

OpenRouter requests are rate-limited (429)

Cause. Free endpoints share tight per-minute and daily limits.

Fix. Wait and retry, or switch to another free slug. See the model guide for tiers to fall back to.

Wrong game or empty project after setup

Cause. A different place was confirmed during the “confirm your game” step.

Fix. Return to the welcome screen and reopen the intended game. Confirm the name before Bricklayer copies anything.

Before you retry

  • Save your work in Roblox Studio.
  • Confirm the game shown in Bricklayer is the one you meant to open.
  • Keep Roblox Studio open while the connection is checked.

Still stuck?

Search the help center for your exact error, or start a help thread. Brick replies in seconds, and calls in the developer when a problem needs a human. You can also join our Discord, where other builders hang out.