Private beta — here's what you'll download
Think of it as an app.
Here's what you get once you're in: AIBOS installs on your Mac, gives you a folder to work in, and runs a caretaker in the background — tidying, checking, and watching over things while you work. Log in, and it syncs with the web server and the web admin interface.
What "download" actually means
Two things get installed. One is yours, one watches over it.
There's no single .exe to double-click — AIBOS installs in two pieces, and they do different jobs.
Your sphere
The folder that holds your whole AI operation — files, memory, agents, all of it. The installer raises it on your machine in one run. It's free and open: the standard behind it has no paywall, ever.
The control panel (aibos-config)
A local app that watches over every sphere on your machine — a dashboard sitting on top of the standard, not part of it. It runs quietly in the background and shows you what's going on, without you having to go looking.
Install it
The real steps, once you're in.
Request access, and this is what happens next: clone the standard, run the installer, and your sphere exists. Open it in Claude Code or Codex, and you're working — no control panel required.
Honest note: the control panel (aibos-config) isn't public yet — it ships with the packaged Mac app, which is still on its way. Everything below gets you a working sphere as soon as you're in, with the nightly caretaker already scheduled and running on its own.
Your sphere is a folder like any other. Open it in Claude Code or Codex, and start talking to your lead agent. The installer already scheduled the nightly caretaker on your machine, so the background job that keeps things tidy is running from day one — no control panel, no extra setup.
The nightly caretaker runs on it today, scheduled automatically by the installer. The menu-bar app and the control panel's background service arrive with the coming Mac app — see the honest notes below for Linux.
What the installer and the control panel both run on.
The free tool that keeps version history of every file, like Google Docs' "see edit history" but for your whole project.
Claude Code or Codex — the tools where AI stops being a chat window and starts working in your actual files. You'll use it to talk to your sphere once it exists.
Coming with the packaged app
A preview of what the control panel gives you.
Eight screens, one dashboard — the aibos-config app isn't public yet, so treat this as a preview, not a today feature.
Context
Shows exactly what gets loaded into a Claude Code session, for any sphere and any agent: every skill, command, rule, plugin, and hook, which layer each one comes from, and the estimated token cost of carrying it all.
It finds duplicates, name collisions, things sitting globally that really belong to one sphere, and dead weight — add-ons you installed once and never touch. Nothing here gets fixed for you yet; it just shows you the truth, clearly enough that you can.
Spheres
Every sphere's health at a glance. It warns you the moment the nightly check hasn't run in over 30 hours, so a quiet failure never sits unnoticed.
The initiative train
Every project across every sphere, laid out as a station line: idea, shaping, building, rollout, running, archived. Click into any one for its full timeline.
The menu
The whole standard, searchable, in plain language — every rule, command, and contract, without needing to dig through files.
Config
Phase BPhase B: per-sphere settings, changed from a dashboard instead of hand-editing files. Every change lands in a tamper-evident log, so you always know what changed and when.
The caretaker
Phase BToday: its schedule, logs, health dashboard, version drift, and decision log, all from one screen. Phase B adds the button to run the nightly job on demand.
Alerts
What's new from the standard, and a morning brief — so upgrades and news reach you without you having to go check.
Health
A self-test confirming the control panel and your standard are actually wired together correctly — plus a Welcome screen for first-time setup, with a "Meet your co-creator" button that opens a terminal right inside your new sphere.
While you're asleep
The caretaker's whole nightly loop, in five steps.
One caretaker per sphere, running headless — nobody talks to it, and it never talks back. You only ever see its results.
Tidy first — automatic cleanup runs, fixing what it safely can.
Inspect — the health check runs next, against a workspace that's already been tidied.
Commit the record — the night's log gets committed and pushed to your own repo, so your disk always has a durable record.
Check the standard for improvements — it looks for a newer version and tells you if one's waiting; it never upgrades without you saying yes.
Propose upward — patterns it keeps seeing become hypotheses sent back to the standard itself, held locally until you release them.
Optional
Sign in, and it syncs. Skip it, and it still works.
The control panel runs fully on your own machine with no account at all. Logging in syncs it with a web admin interface — a hosted dashboard you can check from anywhere.
That's the Cloud Admin plan
Logging in is what connects your local control panel to the web server and the web admin interface — night reports, a sphere dashboard you can check remotely, and health-check monitoring, all in one place.
See pricingHonest notes
Worth knowing before you install.
macOS-first, today
The nightly caretaker itself runs anywhere — launchd on macOS, cron on Linux, scheduled by the installer either way. The menu-bar companion and the control panel's background service are both part of the coming Mac app, and both macOS-specific — Linux gets the standard and the caretaker, just not those two.
The control panel isn't public yet
aibos-config lives in a private repo today, and it ships bundled with the packaged Mac app — the thing you'd actually download and open, still on its way. This page gets the download button the day it exists. Until then, everything you need to raise and run a working sphere is in the install steps above.
Phase A today, Phase B next
The control panel preview above is Phase A: read-only observability — health, timelines, logs, drift, all visible, nothing changeable from the dashboard. Phase B is next: installing and uninstalling capabilities, creating agents, adding spheres, all from the panel, all written to a tamper-evident audit log.
The standard itself
Everything above sits on top of the AIBOS standard — open source is the plan, but the repository is private during the beta. Request access if you'd rather start from the source once you're in.
Request accessYour sphere first. The control panel on top, whenever you're ready.
Two commands raise a working sphere, today. The control panel comes later, with the packaged Mac app.