Rojo DB [Roblox]
The VS Code extension built for Rojo-first Roblox development.
If you're already using Rojo to keep your scripts in a real file system — version-controlled, editor-native, sane — Rojo DB is the layer on top that gives you everything else: a live DataModel graph, two-way Studio sync without breaking your Rojo project structure, Open Cloud DataStore management, AI scripting, Git integration, and a metadata layer for notes and TODOs. All without leaving VS Code.
Why Rojo DB if you already have Rojo?
Rojo solves the file-system problem. Your .luau files live on disk, you can commit them to Git, and Studio stays in sync. That's the foundation.
Rojo DB builds on that foundation instead of fighting it:
- It respects your Rojo project layout. Rojo DB reads your
default.project.json and maps its structure — it doesn't impose its own folder conventions on top of yours.
- DataStores are the missing piece. Rojo has no story for Open Cloud DataStores. Rojo DB gives you a full DataStore browser with version history and export — your live game data alongside your source code, in the same tool.
- Visual DataModel navigation. A live, clickable node graph of your running game's DataModel rendered inline in VS Code. Rojo gets files into Studio; Rojo DB lets you see what's actually in the place at runtime.
- No second sync tool. If you want to push a quick hotfix from VS Code without rebuilding your Rojo project, the Studio bridge handles it. Rojo DB and Rojo can run side-by-side — use whichever fits the task.
- AI scripting that knows your project. Claude integration for generate, explain, and refactor — context-aware because it reads your actual workspace structure, not a generic Roblox template.
In short: Rojo handles source ↔ disk. Rojo DB handles everything the Roblox platform adds on top — the live game, the DataStores, the Studio GUI, the metadata, the iteration speed.
Features
Rojo-aware project discovery. Point Rojo DB at a workspace with a default.project.json and it maps your tree automatically — ServerScriptService/, ReplicatedStorage/, StarterPlayer/, and everything else. Files with .server.luau, .client.luau, and .luau suffixes are classified correctly. No second manifest to maintain.
Live DataModel graph. Your entire running game as a clickable node tree rendered inline in VS Code. Pan, zoom, click to open a script, push or pull individual nodes. Useful for debugging a live place when Rojo's file tree doesn't tell you what's actually instantiated.
Two-way Studio sync. A small plugin runs inside Roblox Studio and talks to the extension over a local HTTP bridge (127.0.0.1, token-auth'd). Save a .luau file in VS Code, it pushes to Studio. Edit a script in Studio, it writes back to disk. Works alongside Rojo — use the bridge for rapid iteration, Rojo for your canonical build.
Auto-installed plugin. No file downloads, no drag-and-drop. The first time you start the bridge, Rojo DB drops the plugin straight into your Studio Plugins folder. Restart Studio once to pick it up, and you're connected.
Open Cloud + DataStores. Full DataStore browser with versions and export. Published-place listing. Messaging Service publishing. The part of Roblox development Rojo deliberately leaves out of scope.
AI scripting. Claude integration for generate, explain, and refactor — bring your own Anthropic API key.
Metadata layer. Attach notes, TODOs, and tags to any script in your project. All stored locally in .rojodb/meta.json — check it into git alongside your Rojo project, or add it to .gitignore.
Git + GitHub. Branch list, status, log, diff, stage, commit — inline in the dashboard. Complements the Git workflow Rojo already encourages.
StyLua + Selene. Lint and format your Luau code with the tools Roblox developers actually use.
Six themes. Void (black + cyan), Oceanic, Sunset, Forest, Rose, Mono. Switch via the command palette, Settings drawer, or during the first-run tutorial.
Getting started
- Install the extension.
- Open a folder containing your Rojo project (with
default.project.json).
- The first-run tutorial walks you through connecting your Roblox account, picking a theme, and installing the Studio plugin.
- Open the Bridge item on the left sidebar and click Start bridge. The plugin auto-installs to your Studio
Plugins folder.
- Open or restart Roblox Studio. The Rojo DB button appears in the toolbar. Click it — the plugin auto-connects to VS Code.
Rojo DB reads your existing Rojo project structure. You don't need to change anything about how you use Rojo.
Commands
All commands are prefixed with Rojo DB: in the command palette (Ctrl+K, or Cmd+Shift+P):
- Connect your Roblox account
- Open dashboard
- Disconnect account
- Sync with Roblox Studio
- Import
.rbxlx place file
- Initialize project in workspace
- Refresh Roblox profile
Inside the dashboard there are ~40 more commands — hit Ctrl+K with the dashboard open.
Settings
rojodb.bridge.port — Port the Studio bridge listens on. Default 34872.rojodb.bridge.autoStart — Start the bridge automatically when the workspace opens. Default false.rojodb.sync.mode — twoway (default), pull, or push.
Requirements
- VS Code 1.85.0 or newer
- Roblox Studio (Windows, macOS, or Linux via Grapejuice)
- Rojo — install it, use it, Rojo DB is built around it
- Optional: an Anthropic API key for AI features, an Open Cloud API key for DataStore features, the
gh CLI for GitHub integration, stylua / selene for Luau tooling
Honest limits
- Open Cloud does not allow direct
.rbxl download, so Rojo DB can't fetch your published places as files. The "Open in Studio" button uses the roblox-studio:// URL scheme instead, which Studio itself handles.
- AI features require your own Anthropic API key. The extension does not proxy through any server.
- Git integration requires
git and optionally gh on your PATH. If they're missing, the Git drawer tells you clearly rather than pretending to work.
- Rojo DB doesn't replace Rojo's build step. Use
rojo build to produce .rbxl/.rbxlx files for publishing. Rojo DB handles the live-development loop.
Privacy
- No telemetry.
- API keys are stored in VS Code's
SecretStorage (OS keychain on macOS/Windows, libsecret on Linux).
- Bridge traffic is local-only (
127.0.0.1) and token-authenticated.
- The project metadata file (
.rojodb/meta.json) lives in your workspace. Check it into git, or add it to .gitignore — your call.
License
MIT — see LICENSE.
Support
