Skip to main content
Studio is where you build everything an Agent uses: interfaces, nodes, skills and the design system behind them. It runs on your machine, reads your files straight off disk, and needs Node and nothing else. No database, no Docker, no account, and it works offline.

​
Start it

Studio is a tool, not a project. Install it, run it in an empty folder, and it sets the project up for you.
1

Install it

Install Studio
Open source and free. No account, and nothing else to install.
2

Run it in a new folder

Start a project
The first time, it asks what to call your project and creates the folders:
You get rx/<your-project>/ with components, templates and styles, plus prompts/ and nodes/, and a first component so Studio opens on something real rather than an empty list.
3

Edit the first component

Studio opens on http://localhost:4108. Open rx/<your-project>/components/welcome/welcome.yaml, change the text, and save. Studio updates as you save.
Run it again inside an existing project and it skips all that and opens straight away. It finds your project by looking for rx/ in the current folder or any parent, so it works from anywhere inside it, and it will not offer to make a second project inside one you already have.

​
What you build here

Everything is a file in your repository. Studio renders what is there, and saving a file updates what you see.

​
Check your work

Studio validates as you go, and it will not let a broken definition be published.

​
Run a node for real

The Nodes tab runs a node against the real service, with no platform running. Fill in the settings, press Run, and the output appears beside them. Keys come from your own .env and are stored nowhere. Testing Nodes covers it.

​
Publish to a universe

Everything up to here is offline. No account, no network, no universe. Connecting is the one place Studio asks you for anything. Connect. Type the address of the universe you are publishing to. Studio asks that universe who authenticates it and signs you in against whatever the answer is, so it names no provider and assumes nothing about how your organisation logs in. You can keep more than one, and switch between them. Publish. Studio checks your work first: if a rule fails, the publish is blocked and you see the problem here rather than as an error from a server. Then it shows you a plan of what would be created and what would change, and nothing is sent until you confirm. A node then waits to be accepted, because it is the only thing you publish that holds a URL and a key. Whoever runs the universe sees the hosts it wants to call and the credentials it needs before it can run. After that first acceptance you publish freely, and it only pauses again if the node reaches for something new. Publishing needs permission on your account, and it is a specific one. Being able to build a workflow does not carry it, because pushing a node the whole universe can use is a different power. If you do not have it, whoever runs the universe grants it.

​
Set up your editor

Everything you author is validated against a schema as you type, so a typo or an unknown field is underlined rather than surfacing later. This works for .json out of the box. YAML needs one extension: Install it from your editor’s extensions panel. VS Code, Cursor and Windsurf all use the same one.
Without the extension, YAML files get no validation at all. Nothing warns you: they simply stop being checked. If you skipped the prompt, search for redhat.vscode-yaml in your editor’s extensions panel.
Each file you author carries a $schema line, which is what the extension follows. To confirm it works, open a node’s node.yaml and delete a required field such as type. A red underline should appear within a second. Undo, and it clears.

​
Next steps

Create your first node

Build an integration as four small YAML files.

Components and templates

Design the interfaces your Agents speak through.

Run the platform

Run a universe yourself: Docker, database, images.