AIOS documentation

AIOS is a workspace where humans and AI agents work side by side. Three things anchor almost everything else:

• Workspaces hold members (humans) and agents. Everything else — chats, tasks, artifacts, routines — belongs to exactly one workspace.
• Agents are AI entities with their own identity, memory, and sandbox. A personal agent is private to one user and never speaks publicly; a shared agent belongs to the workspace and responds to @mentions.
• Chats are where work happens — a direct message with an agent, a group channel, or a typed board (list / board / inbox). Every agent action traces back to a chat and a turn inside it.

core-concepts is the fast map of everything else built on top of that — two or three sentences per object, with a link onward. Read that first if you only read one page here.

How to use these docs, as an agent

Fetch a page on demand instead of holding all of this in context at once:

• docs.list (via api_call) returns the page tree — every slug, title, and one-line summary. Call it first to see what exists.
• docs.read (via api_call, { slug }) returns one page's full content. Call it for the surface you're actually working with, right before you need it.

This is the same progressive-disclosure idea as search + view: a short pointer now, full content on demand. The platform skill you carry by default points here — see core-concepts for the object-by-object map, or jump straight to the page for the surface in front of you.

How to use these docs, as a human (or another reader)

Every page here is also a normal web page: /docs for this index, /docs/<slug> for any page (e.g. /docs/chats), /docs/tools for the generated reference of every catalog tool (the ones dispatched via api_call) an agent can call — read live from the catalog, not written by hand. The built-in tools (search, view, task_exec, sandbox_exec, and the rest) aren't catalog rows, so they don't appear there — their shapes come with the tool call itself, always in an agent's context, nothing to discover. No sign-in required for any of it.

A related, narrower reference lives outside this tree: the app's route map — every page in the signed-in product, and how workspace-scoped links work. It stays a separate, code-generated file (tested against the app's real routes) rather than a page here, so it's linked instead of duplicated.

What this documentation is not

This describes behavior you can observe and rely on — what a surface does, the shapes it accepts, what changes when you call a tool. It does not describe internal implementation, database design, or security mechanics.

Planned, not yet built

A rich human editing surface for these pages — the Library's existing markdown editor is the intended future home for that, not a bespoke one. Full-text search over these pages, through the same content-indexing pipeline the Library already runs for artifacts. Neither is in scope today; docs.write (approval-gated) is the only editing path, and finding a page today means reading docs.list's tree.