Product

Reference, edit and tweak your Roblox place in BloxBot's Explorer

November 5, 2026


Working with an AI agent on a Roblox game used to mean two windows. You asked the agent for a change in one, then switched to Studio to find the part it touched, check a property, nudge a value, and copy a path back into the chat. BloxBot 0.14 rebuilds the Explorer so most of that happens in BloxBot. You see your place, change it, and point the AI at exactly what you mean, in one window.

Reference Roblox objects in chat

The fastest way to get a good result from an AI agent is to name the target. Our analysis of Roblox's OpenGameEval data found the clearest model gains on bounded tasks with a named target. The Explorer makes naming the target a drag and drop:

It works the other way too. When the AI names an object in code formatting, like Workspace.Lobby.SpawnLocation, clicking it opens that object in the Explorer.

Tweak values without asking the AI

Not every change needs a model. Moving a spawn two studs or switching a part's material is faster by hand, and it costs nothing. The 0.14 Explorer shows every property Studio exposes, grouped by category the way Studio groups them, including Position, CFrame and Pivot for parts and Models. Change them in place with:

Attributes have their own tab. You can add, change and remove them, and add and remove tags. Right-click an object to rename, duplicate or delete it where Roblox allows.

Built for big places

The first Explorer read the whole tree at once, which stalled on large games. 0.14 reads objects as they arrive, so Studio no longer freezes on one long read in most places, and the list stays smooth with tens of thousands of objects open. When nothing has changed in Studio it hardly asks at all. It also shows objects below Studio's depth limit, and objects with the same name each get their own row with their own children and values. That matters in real games, where twenty parts called Part is normal.

Services and Terrain show their properties too. Studio's inspect_instance returns nothing for them, so BloxBot reads them with a small read-only script instead.

Careful with your undo history

Anything that runs a script in Studio clears its redo history, which would be a nasty surprise while you're reviewing an AI change. The Explorer stays out of Studio's redo while you look around, apart from once when you first select an object after opening Studio. While there is something to redo, it hides computed values like Mass, which would need a script to read, until there isn't.

How to use the Explorer in your workflow

  1. Ask the agent to build something, for example a checkpoint system for your obby.
  2. Open the Explorer from the top bar and click the object names in its reply to check what it made.
  3. Fix small things yourself: move a checkpoint, change a color, set an attribute.
  4. Drag the part that still misbehaves into the message box and describe the problem.
  5. Run a playtest from the top bar to confirm it works.

Frequently asked questions

What is the BloxBot Explorer?

A live view of the Roblox Studio place your chat is working on, inside BloxBot. It mirrors Studio's Explorer and Properties panels through Studio's MCP server, so you can find an object, change it, or hand it to the AI without switching windows.

Can I edit Roblox properties from BloxBot?

Yes, from BloxBot 0.14. The Explorer shows every property Studio exposes, grouped by category, and you change them in place with dropdowns, a color wheel, a BrickColor palette and X, Y and Z fields. You can also add, change and remove attributes and tags, and rename, duplicate or delete objects where Roblox allows.

How do I reference a Roblox object in a BloxBot chat?

Drag it from the Explorer into the message box, right-click it and choose to reference it, or type @ and its name. You can also right-click a single property or attribute to reference just that value. When the AI mentions an object in code formatting, clicking it selects it in the Explorer.

Does the Explorer work in big Roblox places?

Yes. 0.14 reads objects as they arrive instead of all at once, keeps the list smooth with tens of thousands of objects open, and barely asks Studio anything when nothing has changed.

Does browsing the Explorer mess up Studio's undo and redo?

Not while you look around. BloxBot stays out of Studio's redo history, apart from once when you first select an object after opening Studio. While there's something to redo it hides computed values like Mass, which would need a script to read.

Sources


Back to the guide