Private beta — request access
From nothing to a running sphere.
AIBOS is invite-only today, so this page previews your whole on-ramp, start to finish: clone the repo, run one installer script, and open the folder it creates — a sphere, AIBOS's word for the one folder that holds your whole AI operation — in an AI coding agent like Claude Code or Codex. The commands and the success message below are exactly what you'll type and see once we've invited you in.
Before you start
Three things, and you're ready.
Nothing exotic — the installer is a short script you run once, and the sphere it creates is just a folder with version history.
The plain black-and-white command window already on your Mac or Linux machine, plus git — the free tool that keeps version history of every file, like Google Docs' "see edit history" but for your whole project.
That's what the installer and the nightly check-up are built for.
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.
Clone + install
Two commands, once you're in.
This is what you'll paste into your terminal the moment we invite you in — on the machine where you want the sphere to live. The installer talks you through everything it does, out loud, as it happens.
Required. A short name for your sphere — it becomes the folder name and shows up everywhere the sphere identifies itself.
Required. Your name, written into the sphere's founding file the moment it's created.
Optional. Uses the latest version by default — or name an exact version number to install that one instead.
Optional. Choose where the sphere folder gets created, if not the default spot.
Optional. Skip scheduling the automatic nightly check-up for now.
It's safe to run twice — running it again just confirms everything is still in order, it won't duplicate or break anything. And it checks its own work: the last thing it does is run a health check against the sphere it just built. A clean result is how it finishes. A failed one stops the install and tells you exactly what's wrong, instead of leaving something half-built.
What the installer builds
One run, and all of this already exists.
A working sphere, checked over before the script hands control back to you — everything below is already built and working, not a folder of placeholders.
The first agent born into the sphere — your co-creator and thinking partner, ready to work from minute one.
Exactly one per sphere, and it never talks to you. It runs every night and leaves a short report of what it tidied.
people/<you>/ — a workspace and profile that's yours alone, created the moment the sphere is.
A built-in onboarding track with real memory — it picks up where it left off, session after session.
Scheduled for you on your own machine — maintenance happens while you're asleep.
The sphere keeps a full history of every change, like Google Docs' edit history, starting with its very first save.
Before anything is saved, a check blocks destructive deletes and other commands that could wipe your files.
The installer doesn't call itself finished until that check comes back green.
Once you're invited, here's your first hour
From an empty sphere to real, tracked work.
Open the sphere in Claude Code or Codex
Navigate into the folder the installer just created, and start a session there with your AI coding agent. The sphere is just a folder on your disk — there's nothing else to set up first.
Tell HeadOfSphere what you want to build
HeadOfSphere is your co-creator and thinking partner — the first agent in the sphere, and for as long as you want, the only one you need. Just describe what you're trying to do in plain words. Its built-in onboarding walks you both through the basics together: how the sphere is organized, where things go, and what it is and isn't allowed to do without asking.
Every piece of work gets filed under a thread
Before the first file is written, the work is filed under a thread — think of an email inbox, where every reply folds neatly into the conversation it belongs to. A new thread, or one already open. The tool always refuses to save a file until that's decided; in stricter spheres, it also blocks the very first write until you've made the call.
Already have a mess?
/importer brings an existing company in, on purpose.
Most real companies aren't a blank folder — they're years of scattered docs, half-finished repos, and knowledge that only lives in people's heads. /importer is built for exactly that.
It's made for messy, existing projects: it works in 8 careful steps and stops twice to ask you before anything is moved, so nothing gets reclassified behind your back. Your project keeps its own identity instead of being forked into a copy, and an optional gradual mode lets you migrate a little at a time while the old system keeps running.
It's already in real use, currently at version 0.4.0 — still being built, and honestly marked that way.
Honest notes
Two things worth knowing before you're in.
The commands are Norwegian today
The standard's authors write in Norwegian, so its command names do too. An English version of the whole standard is on the roadmap, still to come. Until then, here's what each command you'll actually type means.
place
receive
save
explore
conform
capability
thread
import
Not invited yet?
AIBOS is in private beta, so the repository is private today — there's no public clone link to fall back on. Request access below, and we'll invite you in as we open up.
Request accessEverything the standard does, in full.
The thread system, the memory architecture, every skill, how the health checks work — documented at the depth it deserves.