A Roblox Studio Explorer + Properties emulator inside VS Code.
Verde lets you view and manipulate your entire Roblox datamodel directly from VS Code, with support for copying, pasting, duplicating, renaming, and deleting instances.
Verde also includes a Properties panel, letting you inspect and modify instance properties without leaving your editor.
Verde works with traditional sync tools (Rojo, Argon, Azul) or with Script Sync + Luau-LSP for sourcemap-based script opening.
Please note that Verde is not a standalone sync tool, it requires one of the aformentioned tools to work correctly.
Features
Full DataModel Mirroring: a 1:1 recreation of your game’s workspace
Script Opening: Double-click scripts from the explorer to open them right in VS Code (works with Rojo/Argon/Azul/Luau-LSP sourcemaps)
Instance Operations: Rename, duplicate, delete, copy, and paste instances
Properties Panel: View and edit instance properties right from VS Code
Attributes + Tags: assign, edit, rename both attributes and tags for any instance
Yes, I can add it on there no problem. In the meantime if you are eager to try it, there are a couple of tools that exist that can take vs code marketplace links and generate a vsix out of them.
This is a tool that has worked for someone trying to install in Cursor before.
Regardless I will publish it on OpenVSX later today!
This is a gem! When combined with Azul, I get the best of both worlds. Thanks a ton for this wonderful resource!
Just a question! When using Cursor or any other AI agent, is there a way to give the LLM context of the Verde explorer/properties window? If not, do you think that’s possible?
Currently not possible with the current state of Verde but I have thought about this. One way to do this is to create an MCP server with tools that would let an AI agent manipulate the explorer or properties window, and in turn, manipulate your game via Verde.
I am very open to doing this in the future, maybe when I have some more time to focus solely on Verde, as I am currently close to releasing a game.
After using this for some time, I noticed some problems. Here they are:
1 - When I playtest the game and stop, the plugin gets disabled and I need to enable it again.
2 - When I insert a ModuleScript inside another one and rename it, a new module is created with the name I set, and the previous one is deleted. I’m not sure if this is supposed to work like this.
ctrl+hover no longer shifts focus in the Verde Explorer when the symbol resolves to a definition in a different file (imported modules or packages).
The Verde Explorer no longer auto-reveals itself when switching scripts. Script focus updates only occur when the Verde view is already visible. (so you can now hide the sidebar with Ctrl+B and verde will not force it back open)
Ctrl+P Quick-Pick menu to quickly navigate to instances
undo/redo support for all operations, including bulk operations like mass-deleting instances
ability to preview Sound instances from the Verde explorer. If it does not work, make sure to turn the Only Play Audio When Window In Focus Studio setting off.
Better Roblox Studio parity with Color3 properties
Better handling of readonly properties
Proper display of CFrame properties
Plugin
Remove dependency on API dump module (and therefore s3), now using ReflectionService
Hey, I’m having some trouble with opening scripts using the Verde VsCode explorer while collaborating with my friend using the collaboration feature. Everything else works fine though, and I can access the scripts through the normal explorer, just not the Verde one
EDIT: When trying to open a script while collaborating in verde, it breaks the regular explorer too so I have to restart Vscode
Really cool (and much needed) tool, I have been testing it for a while and the ability to inspect the game’s instances without switching to Studio saves a lot of time. It will definitely be replacing my current explorer.
But I was wondering if it was possible to add a configuration window or simple toggleable UI like Argon/Rojo so a different host and port can be used to match my current configuration. Along with it, a way to pick different icon sets for the explorer (Vanilla for example) whouldn’t be bad.
Good ideas, definitely on the list of things to do. When I have time I will be adding a settings popup for sure. Also on the list is some better UX such as items in the explorer don’t automatically expand their children when clicked on.
Different icon sets are a nice idea, I’ll have to see where to source those, but shouldn’t be a problem to implement into verde as an option.
When you say “collaboration feature”, do you mean team create? Is your friend also editing a script using Verde?
Verde uses the sourcemap to open scripts. So, if the script cannot be opened, that just means that it does not exist in your sourcemap. That is not the job of Verde to maintain, it is up to whatever sync tool you use (Rojo/Azul, etc). Verde simply reads it to figure out the file path of the script on your computer and opens it in vscode.
