Luu Code hands your coding agent the keys to your open place. It reads the DataModel, edits scripts, presses Play, watches the output, clicks around the running game, takes screenshots, and fixes what it broke — while you watch.
You bring Claude Code, Codex, or a model on your own machine through Ollama. Luu Code brings Studio. No credits, no API key, no AI of its own.
| Look around | Services, instance trees, properties, attributes, tags, your selection, script source, what a class actually has |
| Change things | Create, delete, rename, reparent, clone, set properties, edit scripts, replace a pattern across every script at once |
| Playtest | Start and stop Play and Run mode, restart, wait for the game to be ready, give the link real latency |
| Read output | Everything Studio prints, including the error your last change caused and the ones from before it connected |
| Work out why | Log any line without touching the script, and profile which functions the frame time went into |
| Poke the game | Players, characters, PlayerGui, the camera, and Luau it runs live |
| See the screen | Screenshots of Studio, handed straight to the agent |
| Play the game | Keyboard, mouse, and clicks on real on-screen buttons |
| Bring things in | Search the Creator Store and drop models, meshes, images, audio, and animations into the place |
- Download Luu Code and run the installer — Windows.
- Open Settings → Updates, press Install next to the Studio plugin, and restart Studio. The app carries the matching plugin.
- Have Claude Code or Codex installed and signed in. Luu Code drives whichever you have.
Running models locally? Pull one that supports tool calling in Ollama and it appears in the model picker beside the rest. Ollama models are run by the Codex CLI, so keep that installed too.
Prefer to install the plugin yourself? LuuCode.rbxm is attached to every release; drop it in Studio's Plugins tab → Plugins Folder.
The app, the Studio plugin, and the MCP command ship from one release, so they cannot end up on different versions. A new build shows up in the sidebar.
Nightlies are published on the releases page alongside the stable builds. They wear a purple icon, install beside the release build, and carry their own plugin as LuuCodeNightly.rbxm — run both, neither overwrites the other. A nightly only ever updates to another nightly.
- Open your place in Roblox Studio.
- Open Luu Code.
- Pick a model, and say what you want changed.
Try:
The shop errors when I click Buy. Play it, find out why, and fix it.
Make the lobby spawn brighter, then show me a screenshot.
Chats are saved per place. Open a place and its history is there.
The chip beside the send button holds seven switches — looking, editing, playtesting, running Luau, sending input, screenshots, the Creator Store. Flip one mid-conversation and the agent is told it no longer has it.
Everything runs on 127.0.0.1 and nothing is sent anywhere. The plugin connects to the server on this machine as soon as both are open.
Luu Code works through Studio. It does not read or write your files.
The same Roblox tools are available over MCP, so you can skip the app. The server ships inside Luu Code; there is nothing to install. Settings → Connection has the exact command for your install, ready to paste into Claude Code or ~/.codex/config.toml.
It joins a running Luu Code server, or starts one. Only Studio has to be open.
Building Luu Code from source, adding Roblox operations, and supporting another coding agent are all covered in CONTRIBUTING.md.
MIT. See LICENSE.