Studio Bridge / v 7.6 / Plain Lua · auditable

A submarine with a sonar.

The plugin doesn't think — that's the browser's job. It listens for the agent's tool calls, executes them locally in your project, and reports the outcome back. Quiet, transparent, and the only thing on this hull is what you can read in the source.

Pisces · Web Connector

v 7.6 · 14 ms

API Key pk-live-f3e9·······a8c4

● Connected

Baseplate · 4924918399 last poll 0.4s ago

HTTP allowed Script edits allowed Indexed 128 scripts Snapshots live

Install from Marketplace → Setup walkthrough

What's inside.

The Web Connector is a single Lua plugin — about 3,300 lines — that does four things: handshake, index, poll, execute. Nothing more.

It does not contain a model, a parser, an LLM client, or a UI for chatting. All of that is in the browser. The plugin is the part that touches your project, and we kept it small on purpose so you can read it.

Tools the plugin can execute

read_scripts grep_scripts create_script edit_script fix_script delete_script create_part create_model create_folder create_remote_event create_remote_function create_tool create_weld spawn_rig set_property set_properties delete_instance inspect_instance read_properties playtest_verify

Permissions, in plain English.

Studio asks you to allow two things on first connect. Here's exactly what each one does and why we need it.

Permission · Allow

HTTP requests

The plugin talks to one host: pisces-agent…us-east4.run.app. Long-poll for tool calls, send back results. Nothing else outbound, nothing third-party, nothing automatic.

Permission · Allow

Script editing

Lets the plugin create, edit, and delete scripts when the AI emits a tool call. Every single edit is recorded as one ChangeHistoryService entry — Ctrl+Z restores instantly.

Implicit · Studio default

Selection access

Reads what you have selected when you ask Pisces about the current instance. Read-only, no writes through this surface.

What you won't find in the source.

No loadstring. Nothing is dynamically evaluated.
No remote require. The plugin doesn't pull module IDs from the cloud at runtime.
No getfenv / setfenv. No environment hacking.
No telemetry. No analytics SDK, no third-party pixel, no fingerprinting. The server only sees what you typed and the tool results that came back.
No background activity. When you click Disconnect (or close Studio), the polling loop stops within ~1 second.

Open pisces_web_plugin.lua on the public repo and read it end-to-end if you want — it's not minified, not compiled, not a single obfuscated require shrugging at you. The whole point of the bridge being open is that you can verify everything we just said.