Skip to content
02 · Build on it

Build on the object graph, not inside a silo.

Apps become replaceable providers and views over one typed system. You publish typed actions and data sources; the OS gives them semantic history, capability-scoped access and inspectable agent plans — for free.

The surface you build against

Four contracts.

Entity & action contract

AOS-ARCH-005

Register a data source or a typed action over shared entities — person, project, document, event, message. No private state path; everything is contract-first, declared in a transport-neutral IDL that generates Rust bindings.

Capability-scoped agents

AOS-ARCH-010

Agents get exactly the authority you grant — least privilege by construction, revocable, and every effectful action leaves a receipt with an undo path. No ambient UI control.

Lawful service integration

AOS-PROD-014

Reach services by the highest lawful method: official APIs, regulated interfaces like open banking, interop standards. Never defeat pinning or anti-tamper on someone else’s app.

Native clients, full features

AOS-PROD-014

A native client gets entities, IntentBox actions, history, capabilities, instant-mode participation, offline and agent access — or it isn’t native. A two-floor model runs unmodified apps as guests for breadth.

Interop by design

FIDL internally, MCP externally.

Platform agent coverage today is opt-in per app — the assistant only sees what a developer bothered to annotate. In Agent OS, coverage is 100% by construction: every action and every byte passes through the entity/capability layer, so there is nothing to annotate. The entity/action registry is exportable as an MCP server, so the external agentic world can work with Agent OS on day one.

Build on it.

The platform is specified end-to-end. Join the waitlist for the SDK preview and early developer access.

No spam. A research programme — you’ll hear from us when there’s something real to try.