Help

Connect Roblox Open Cloud safely

Optional. What Open Cloud adds, why to test it on a throwaway game first, and the smallest key that works.

Updated November 8, 2026

You do not need Open Cloud for normal Bricklayer use. Set it up only if you want the agent to publish a saved place file, read place versions, or read experience analytics.

Start with a throwaway game

An Open Cloud key acts like a password for your experiences. Test with a game you would not mind losing:

  1. Make a new private Baseplate named Bricklayer Open Cloud Test.
  2. Publish it as a new private experience.
  3. Use File → Save to File to make a fresh .rbxl copy.

You can delete the experience and the key after the test.

The smallest key that works

On the Creator Dashboard, under API Keys:

  • Turn on Restrict by Experience and choose only the test experience.
  • Add only these permissions: universe-places:write, universe.place:read, and universe.analytics:read.
  • Pick a short expiration, such as one day.

Never paste the key into an AI chat, a project file, Git, a screenshot, or this forum. Bricklayer reads it only from the process you launch with it.

Launch Bricklayer with the key

The key is passed to Bricklayer when you start it, so it never sits in a file. The exact PowerShell and Terminal commands are in the step-by-step guide: Connect Roblox Open Cloud safely.

When you are done

Quit Bricklayer, disable or delete the key on the Creator Dashboard, and archive or delete the test experience. Never reuse a test key for a real game.

Did this answer your question?

Still need help? or start a thread in the community forum.