Install Cerevisor
Download, install, and launch Cerevisor on Windows or macOS.
Cerevisor ships on Windows and macOS. A Linux build is available but unsupported.
Download
Download the latest installer for your platform from cerevisor.com/download.
| Platform | Installer | Notes |
|---|---|---|
| Windows 10/11 | CerevisorSetup-<version>.exe |
Branded installer chrome; standard "Next, Next, Install" flow. |
| macOS (Apple Silicon, M1+) | Cerevisor-<version>-arm64.dmg |
Pick this one for any Mac with an Apple chip (M1, M2, M3, M4). |
| macOS (Intel) | Cerevisor-<version>-x64.dmg |
Pre-Apple-Silicon Macs only. |
We deliberately ship per-architecture macOS DMGs instead of a fat universal binary. A build made for your Mac's chip is significantly smaller and more reliable. Pick the matching architecture for your Mac. Installing the wrong one yields a launch error.
If you're not sure which Mac you have: click the Apple menu → About This Mac. If it says "Chip: Apple M…", you want arm64. If it says "Processor: Intel…", you want x64.
Install
Windows
Double-click the downloaded .exe and follow the installer. Cerevisor installs for all users and asks for administrator approval once during install. You can change the install location if you want, and it adds a Start Menu shortcut.
macOS
Double-click the downloaded .dmg. Drag the Cerevisor app icon to your Applications folder. Eject the DMG when done.
The first time you launch Cerevisor, macOS may show a "Cerevisor cannot be opened because the developer cannot be verified" warning. This is normal: the early builds are signed ad-hoc, not yet with an Apple Developer ID certificate. To allow the launch:
- Right-click (or Control-click) Cerevisor in Applications.
- Choose Open.
- Click Open in the confirmation dialog.
After the first allow, future launches behave normally. Apple Developer ID signing + notarization is on the roadmap.
First launch
The first time Cerevisor opens, Home shows two choices: Guide me through my first project and Explore on my own. Nothing opens on its own — no tour, no setup dialog. Choosing the guide walks you through building and running your first workflow. Choosing Explore on my own takes you straight to the normal Home screen; the guide button is still there whenever you want it.
Either way, you connect a model provider and choose your trust setting (how often Cerevisor should pause to ask permission before doing risky things, like writing files or running shell commands) only when you choose to — from the guide, or later from Settings. You can't actually run a workflow until at least one provider is connected. See Connect a model provider.
Updating Cerevisor
Cerevisor checks for updates in the background on launch. When a new version is available, you'll see an "Update available" indicator in the title bar and a branded modal appears with Restart now / Later options. Picking Restart now applies the update on the next launch.
Updates always download regardless of your license tier. Paid customers can never be stranded on a broken build by a license-server hiccup.
Where Cerevisor stores its data
Cerevisor is local-first. All user data lives under your home directory:
| Folder | What's in it |
|---|---|
~/.cerevisor/ |
The root of all Cerevisor user data. |
~/.cerevisor/skills/ |
Skills you've created in the Skill Workshop. |
~/.cerevisor/memory/ |
Your profile, harness self-memory, observations, freeform memory entries. |
~/.cerevisor/audit-logs/ |
NDJSON audit trails from every workflow run. |
~/.cerevisor/cloud-artifacts/ |
Files downloaded from Cursor cloud runs. |
~/.claude/skills/ |
Skills you've installed for Claude Code; Cerevisor also picks these up automatically. |
On macOS, the equivalent of ~ is /Users/<your-username>/. On Windows it's C:\Users\<your-username>\.
Uninstalling
Windows: Use Settings → Apps → Installed apps → Cerevisor → Uninstall.
macOS: Drag Cerevisor from Applications to the Trash.
By default, uninstalling leaves ~/.cerevisor/ and ~/.claude/skills/ in place. If you also want to remove your data and skills, delete those folders manually after uninstall. (Back them up first if you might come back: the folders are portable; reinstalling and restoring them brings everything back.)