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.
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 open source under AGPL-3.0 — free to use in your games (free or commercial) and free to modify. You'll need your own access to an AI client (e.g. Claude Code). The 's&box Claude Bridge' / 'sboxskins.gg' name and branding aren't licensed for reuse, but the code is open.
What do I need to run it?+
s&box (installed via Steam), Node.js 18+, and an MCP client — Claude Code is recommended because the one-command plugin bundles the cookbook brain, the specialist agent, and the screenshot workflow. The bridge works on Windows, Linux, and macOS.
Do I have to use Claude Code?+
No. The bridge's MCP server works with any MCP client via npm (claude mcp add sbox -- npx sbox-mcp-server@latest). 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 MCP server and the s&box addon talk over local file IPC — no network, no open ports (s&box's sandboxed C# blocks sockets entirely). The AI client you use has its own privacy terms, but the bridge itself doesn't phone home.
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?+
Reinstall the addon from the Asset Library when a new version drops. The MCP server updates itself — the plugin always pulls the latest, or npx sbox-mcp-server@latest grabs it on the next session. Keep the addon and the server on the same major.minor version.
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