The first public build ships ready.
Cerebro will open publicly only as a signed and notarized macOS app. Until that release gate is complete, there is no public artifact.
Get the signed beta first.
Join for important release notes and the public-beta launch when email delivery resumes.
0.1.0 (beta)TBDmacOS 14+ · Apple silicon0000000000000000000000000000000000000000000000000000000000000000What the public beta expects.
Cerebro is the native operating layer. Claude Code and Codex remain provider tools you install and authenticate separately.
Mac
macOS 14 or newer on Apple silicon. Intel support is not promised for the first beta.
Provider
Install Claude Code, Codex, or both. Your provider account covers model access and usage.
Workspace
Choose the projects and connected services Cerebro may operate for the mission.
The build must prove the real operating loop.
The release gate covers more than packaging. The public build must demonstrate the autonomy model and its evidence.
- Top-level autonomous preset. Full Operator or the current equivalent is selected deliberately.
- Conductor orchestration. A mission delegates and advances across agents.
- Durable memory. Working state survives a provider session.
- Recorded results. Audit and run history explain completed work.
- Provider handoff. Claude and Codex can swap without losing the thread.
- Project Workers. Background work returns a report with provenance.
Four steps to the first mission.
Install a provider CLI
Follow the official Claude Code or Codex installation and sign-in flow.
Open the signed app
Move Cerebro to Applications and launch it normally.
Select the operating boundary
Choose the top-level posture, workspaces, and connected services for the mission.
Brief the Conductor
State the outcome, assign the fleet, and watch Mission move.
Release questions.
Can I get a build today? +
Not from this site while the release gate is closed. Join the waitlist for the signed public beta.
Does Cerebro include Claude or Codex usage? +
No. Bring your own provider installation and account; usage remains governed and billed by that provider.
What does local-first mean here? +
Projects, agent state, receipts, and connected knowledge are owned by the native app on your Mac. Provider requests and services you deliberately connect still use their own network paths.
Can I stop an autonomous mission? +
Yes. The operating model keeps pause, stop, redirect, status, and recorded results at the mission level.