Hive

The problem

Point three AI agents and two teammates at one Roblox game and you get chaos: one agent rewrites a file another is halfway through, nobody knows which remote name was agreed, and somebody stops a playtest that someone else was running.

Hive fixes this with a coordination layer that sits between your editors/agents and Rojo. Everyone, human or agent, reads and writes the same live project and sees the same context.

 Editors (humans) ──ws / CRDT──┐
 Agents (Claude, Codex…) ─MCP──┼──►  HIVE  ──files──►  Rojo (unchanged)  ──►  Roblox Studio
 Studio edits ◄────────────────┘   live docs · claims · ledger · playtest lease
                                        ▲
                                        └── StudioMCP: screenshots, play/stop, console

Related MCP server: Roblox Studio MCP

What makes it safe

See and playtest the game

Open http://localhost:7777/ for a live viewer: edit-mode viewport, ▶ Playtest / ■ Stop, active claims, activity feed and the Studio console. Agents get the same abilities through MCP, so Claude can look at the game, run a playtest, read the console and report back.

Agent tools (MCP)

Quick start

npm install
node src/server.js /path/to/rojo-project     # Hive on :7777
rojo serve                                   # in the same dir, for Studio sync

Register the MCP bridge with each agent (give each its own name):

{ "mcpServers": { "hive": {
    "command": "node", "args": ["/path/to/hive/src/mcp.js"],
    "env": { "HIVE_ACTOR": "agent-combat", "HIVE_URL": "http://localhost:7777" } } } }

Studio control uses Roblox's StudioMCP binary (macOS default path; override with STUDIO_MCP=).

npm test      # 13 tests

Layout

src/core.js     Hive: CRDT docs, claims, ledger, playtest lease (pure, no I/O)
src/server.js   disk mirror + WebSocket sync + HTTP API + viewer
src/studio.js   StudioBridge: screenshots (cached), play/stop, console
src/mcp.js      MCP tools for agents
src/viewer.html live viewer

Status

Working: core, server, MCP tools, Studio bridge, viewer, tests (Studio is faked in tests; live-Studio verification is pending).

Roadmap:

• VS Code extension: Yjs binding, presence cursors, claims panel

• Non-script instances (parts, properties) via a Studio plugin

• Playtest-time viewport capture

• Auth and multi-project hosting

• Code-OSS fork once the extension proves out

Credits

Builds on Rojo (MPL-2.0) and Yjs. Not affiliated with Roblox Corporation.

License

MIT