Studio plugin and bridge
Install the NexusRBX Studio Bridge plugin, pair it with the AI workspace, and understand how safe Studio reads and writes work.
Install the plugin
- 01
Use the generated install target
Install roblox-plugin/NexusRBXStudioBridge.plugin.lua when you are working from this repository. The source folder is not the Studio install artifact.
- 02
Open Roblox Studio
Place the .plugin.lua file in the local plugins folder or install it through your normal Studio plugin workflow.
- 03
Pair from the workspace
Open /ai, start Studio pairing, and enter the short-lived code in the plugin panel.
Relevant repository files
roblox-plugin/NexusRBXStudioBridge.plugin.luaroblox-plugin/build/bundle-plugin.jsroblox-plugin/src/backend/src/lib/studioToolProtocol.jsdocs/studio-tool-protocol.md
Safe inspection
NexusRBX should not send the full place source to the model by default. Studio-aware work begins with get_project_manifest, then search_project or search_source, then targeted read_script calls for the specific script that matters.
{ "protocolVersion": "2026-06-20-phases1-9", "command": "get_project_manifest", "reason": "Find likely round-system scripts before reading source"}Write protection
- Known Studio script edits include expectedSourceHash.
- Stale edits return source_conflict so the workspace can re-read before retrying.
- Destructive commands snapshot first and include snapshot IDs in the acknowledgment.
- Unsupported runtime actions return structured errors with a reason instead of pretending to succeed.
{ "operation": "write_script", "targetPath": "ServerScriptService/RoundController", "expectedSourceHash": "sha256:previous-source-hash", "applyMode": "manual_review"}Manual Review
- Confirm the target path is the script or instance you expected.
- Check whether the change creates RemoteEvents, ModuleScripts, or GUI objects.
- Run Play Solo or Start Server depending on whether the code affects client-only or multiplayer behavior.
Was this page helpful?