Check that your computer is compatible
VibeStarter runs your agents in a Linux virtual machine that comes with the app. This virtual machine sets the required configuration: it needs its own memory, CPU cores, and disk space.
The two supported systems
Section titled “The two supported systems”Windows 10 or Windows 11, 64-bit, on an Intel or AMD x86-64 processor.
Windows on ARM (Snapdragon, Copilot+ PCs) is not supported.
macOS 15 or later, on an Apple Silicon chip (M1 or newer).
Macs with an Intel processor are not supported.
There is no Linux version of VibeStarter, and none is planned.
The expected configuration
Section titled “The expected configuration”| Item | Minimum | Recommended |
|---|---|---|
| RAM | 6 GB | 8 GB, 16 GB to be comfortable |
| CPU | 2 threads | 8 threads or more |
| Free disk space | 5 GB | 20 GB |
An Internet connection is required at all times: the app talks to your account, and your agent talks to its AI provider.
What the app checks on first launch
Section titled “What the app checks on first launch”The first step of the startup wizard is called Hardware. It checks six lines: Operating system, Memory, CPU, Acceleration, Disk space, and VM bundle.
The verdict is shown as a heading: “This PC is ready”, “This PC can run VibeStarter”, “This PC is very constrained”, or “This PC needs attention” — with “Mac” variants on a Mac.
| Check | Blocks startup | Shows a warning |
|---|---|---|
| Memory | less than 6 GB | less than 8 GB, then less than 16 GB |
| CPU threads | fewer than 2 | fewer than 8 |
| Free disk space | less than 5 GB | less than 20 GB |
| System and architecture | anything other than 64-bit Windows or Apple Silicon Mac | — |
You can get past a warning with Continue anyway or Continue despite the risk. A block cannot be bypassed: the Hardware step has no button to get past it. The Copy diagnostics button copies the details of all six lines to the clipboard.
This step comes before the sign-in step. You can therefore install the app and have your computer checked before you buy.
Hardware virtualization
Section titled “Hardware virtualization”This is the CPU feature that lets the virtual machine run at full speed.
It is called VT-x on Intel and AMD-V (“SVM”) on AMD, and it is turned on in your motherboard’s BIOS or UEFI.
To check it in thirty seconds: press Ctrl + Shift + Esc, open the Performance tab, go to the CPU section, and look at the Virtualization line. It must say Enabled.
Nothing to turn on: Apple Silicon Macs provide virtualization natively.
Without it, VibeStarter still starts, using software emulation, which is much slower, and new Blender computations are unavailable. The Welcome step then shows “Hardware virtualization disabled”, the message “Acceleration inactive: reduced performance and new Blender computations unavailable.”, and the advice that matches your system. In the app, a “Reduced performance mode” banner reminds you of this, with the View diagnosis button — see The app won’t start.
Limits
Section titled “Limits”- No Linux version, no Intel Mac, no Windows on ARM.
- The virtual machine reserves a share of the installed memory, a little under half, and never less than 3 GB: about 3 GB out of 8 GB, 6 to 7 GB out of 16 GB. The number of agents you can run depends on what is left.
- The app needs a permanent Internet connection.
Frequently asked questions
Section titled “Frequently asked questions”Does it work on Mac? Yes, on Apple Silicon Macs running macOS 15 or later. See Install on Mac.
Can I try it before buying? There is no trial version. However, the app is free to download, and the Hardware step checks your computer before any connection to an account. The purchase terms are on Buy VibeStarter.
I have 8 GB of memory. Is that enough? It is above the minimum, but only just. The virtual machine takes about 3 GB, and Roblox Studio and your browser take the rest. With 8 GB, plan on running only a few agents at once — see Run and steer your agents.
VibeStarter uses a lot of memory. Is that normal? The virtual machine’s memory is counted together with VibeStarter’s in Task Manager: it is the same line. The environment uses a share of the installed memory, a little under half: about 3 GB out of 8 GB, 6 to 7 GB out of 16 GB. This is expected.
My CPU doesn’t support hardware virtualization. Can I still use it? Yes, with software emulation, as long as the other checks pass. Expect agents and builds to be much slower, and new Blender computations to be unavailable: creating models with Blender is paused for as long as acceleration is inactive.