What is the Claude Bridge for s&box?+
It's a tool that lets an AI (Claude, or any MCP client) work inside your s&box editor, writing C# scripts, creating GameObjects, wiring components, building scenes, and assembling whole game systems. You describe what you want in plain English; the AI builds it, screenshots its own work, and fixes it.
What changed in v2.0?+
v2 moved the bridge onto s&box's built-in editor MCP server (in the editor since July 2026, on by default): streamable HTTP on port 7269 instead of file polling, screenshots returned inline as images in the tool result, live tool discovery via search_tools across 28 described toolsets, permission hints on read-only tools, real error semantics, scene checkpoints with rollback, and no Node.js requirement on the main path. Tool names are unchanged from v1.x; six tools are now served by native built-ins with the same names. Connecting is one command: claude mcp add --transport http sbox http://127.0.0.1:7269/mcp.
Do I need to know how to code?+
No, that's the whole point. It was built for people who have game ideas but don't necessarily know how to code. You describe what you want and the AI writes the scripts, creates objects, and wires up systems that would otherwise be out of reach. Knowing some s&box concepts helps you steer, but it isn't required.
Is it free?+
Yes. The bridge is free to use for building your s&box games, free or commercial, and you can modify it locally. It's source-available (no redistribution): you may not redistribute, fork, mirror, or re-host the bridge itself, and the 's&box Claude Bridge' / 'sboxskins.gg' name and branding are trademarks. The games you make with it are entirely yours. You'll need your own access to an AI client (e.g. Claude Code). Versions released before July 2026 remain available under AGPL-3.0.
What do I need to run it?+
s&box (installed via Steam) and an MCP client. Claude Code is recommended because the one-command plugin bundles the cookbook brain, the specialist agent, and the screenshot workflow. Since v2.0 the editor hosts the MCP server itself, so Node.js is no longer required for the main path, you only need Node 18+ if you add the optional lifeline diagnostics server.
Do I have to use Claude Code?+
No. The editor's MCP server speaks streamable HTTP on 127.0.0.1:7269, so any MCP client can connect (in Claude Code that's claude mcp add --transport http sbox http://127.0.0.1:7269/mcp). Claude Code just gives you the full experience: the bundled brain, agent, and skills, in one command. With another client you wire those in yourself.
What is the "brain" (sbox-cookbook)?+
The hardest part of building an s&box game with an AI isn't typing C#, it's knowing the right pattern (how shipped games structure an inventory, keep money host-authoritative, version a save file). sbox-cookbook is a code-grounded knowledge base mined from real, shipped, open-source s&box games. Ask for a system by name and the AI reaches for a proven recipe instead of guessing.
Is it safe? Where does my data go?+
Everything stays on your machine. The editor's MCP server binds to loopback only (127.0.0.1:7269), nothing is exposed to your network, and the bridge itself doesn't phone home. The AI client you use has its own privacy terms.
Can it build a whole game?+
It's excellent at coding game systems through conversation: player controllers, NPC AI, networking, UI, inventories, economies, save systems, and whole genre loops the way shipped games do. It's serviceable at map building (it can screenshot and check its own work, but final visual polish still wants your eyes). Think of it as a tireless coding assistant inside the editor, not a one-click game generator.
What can't it do well yet?+
Particle authoring: s&box compiles particles in its own particle editor, not through the bridge. The AI can play a compiled .vpcf effect, but you build the effect in-editor first. Final visual/art polish on maps also still benefits from a human eye.
Does the Claude Bridge dock need to stay open?+
No. That was true in very early versions, but since v1.3 the bridge runs on a static frame handler that processes requests whether or not the dock is open. The dock (View → Claude Bridge) just gives you a status readout if you want it.
How do I update it?+
Update the claudebridge library from the Asset Library when a new version drops. The tool surface lives in the addon, and toolsets hot-register within seconds of a clean compile. The MCP server itself ships with the s&box editor, so it updates with the editor. The optional lifeline updates itself (npx pulls the latest sbox-mcp-server@2 on the next session).
Where do I report bugs or request features?+
Open an issue on GitHub (github.com/LouSputthole/Sbox-Claude) or email sboxskins@gmail.com. Including your get_bridge_status output and get_compile_errors makes bugs much faster to fix.
Ready to build a game by talking to an AI?
Get started