From install to your first agent session.

Before you start

Download the installer, check its SHA-256 and run it. Until it is code-signed, Windows SmartScreen asks first: here is what to do. RoVibeCoder installs for your Windows user and adds the WebView2 runtime if your PC lacks it. You also need Roblox Studio, installed from Roblox, an account or API key for your AI agent, and a RoVibeCoder license: the download is free, but the app works only with an active license, which you buy on our Discord server.

Account

1. 01 Activate your license

   The step opens the Account page: paste the license key we sent you in a Discord direct message and select Activate. The app unlocks, fetches your skill packs and keeps them up to date. Until a license is active, the app stays locked and the steps below wait. No license yet? Buy one on Discord. Renew it there before it ends; your key stays the same.

Agent runtime

1. 02 Install QEMU

   QEMU is the free program the agent VM runs on; it is not bundled. The step installs the official package with winget, which opens in a window of its own and asks its own questions, while the QEMU installer asks Windows for permission. No winget on your PC? Download QEMU from qemu.org instead, or choose the folder you installed it to.

2. 03 Turn on hardware acceleration Optional

   Windows Hypervisor Platform lets the VM run at full speed; without it, it runs in software emulation, about ten times slower. RoVibeCoder only checks it: Windows settings are yours to change.

   1. The step opens Turn Windows features on or off. Tick Windows Hypervisor Platform, select OK and restart.
   2. If the step still says the hypervisor does not run, turn on virtualization (Intel VT-x or AMD SVM) in your PC’s UEFI or BIOS settings, then select Check again.
   3. Virtualization is on and a restart did not help? Windows may be set not to start its hypervisor at boot, as some other emulators and VM programs do. Open a terminal with Run as administrator, run bcdedit /set hypervisorlaunchtype auto, restart Windows, then select Check again.

3. 04 Prepare the Linux VM

   The step downloads the Ubuntu 24.04 base image (252 MB, checked against a pinned SHA-256) and starts the VM. The first start installs Ubuntu packages, Node.js and the agent CLIs you picked on the Agent runtime page (all four by default), which takes a few minutes once; later starts are quicker. CPUs, memory and the storage folder are set on the same page.

Roblox Studio

1. 05 Install the RoVibeCoder Studio plugin

   RoVibeCoder’s own plugin lets agents read the open place and, when you allow it, change it and run playtests. The step copies the plugin that comes with the app into Studio’s local plugins folder (%LOCALAPPDATA%\Roblox\Plugins). Studio loads it the next time it starts. After an app update the step may offer Update plugin.

2. 06 Install the Rojo Studio plugin

   RoVibeCoder includes Rojo, which syncs your project’s files into Studio, so you do not install Rojo yourself. The step installs Rojo’s Studio plugin from that same Rojo, so plugin and server always match. Prefer your own Rojo? Pick it under Which Rojo runs in a project’s Rojo panel.

First session

1. 07 Create your first project

   Select New project, name it and pick a template: Blank, Obby, Tycoon or Simulator. Projects go to Documents\RoVibeCoder unless you choose another folder. Every project comes with instructions for the agents (AGENTS.md, CLAUDE.md, GEMINI.md) and starter skills. Already have a Rojo project? Use Import folder.

2. 08 Pair Studio with the project

   1. Open a place in Studio (an empty Baseplate is fine). In the project’s Rojo panel select Start, then connect Rojo’s plugin in Studio to the port the panel shows.
   2. In the project’s Studio panel select Pair Studio and copy the pairing string. It works once, for 5 minutes.
   3. In Studio, open the RoVibeCoder plugin from its toolbar button and paste the string. Studio asks once whether the plugin may connect to 127.0.0.1: allow it. The plugin talks to nothing else.

3. 09 Connect an agent

   Select Launch agent, keep Run in: VM and pick your CLI. The first time, it signs in inside the VM with your own account or API key; it shows a link or a code to finish in your browser. The sign-in stays in the VM.

   Agents can read the place right away. To let one change it (write scripts, insert models, start playtests), switch it on under Agents allowed to change the place in the Studio panel. Then describe what you want to build.