A durable thread, over disposable sessions
One Conversation , published once, rides a succession of disposable Sessions — upgraded in place ( migrate ), retired cleanly ( drain), even across providers — with its full lineage and audit trail preserved throughout.
Every serious agent app hand-builds this.
Durable threads over ephemeral runtimes; version pinning; clean cutovers; an audit trail an auditor will actually accept. Teams reinvent it in-house, badly, every time. OASP standardizes it — so the hard part is a spec you adopt, not a system you maintain.
Eight resources, at a glance
The whole protocol is a small, closed set of resources and the interactions between them.
The versioned contract an agent is deployed from.
A running instance of an AgentDefinition.
The durable, user-facing thread. Outlives its sessions.
A disposable, provider-side execution context.
An append-only record on a Session: send, stream, tool-call.
An identity acting in the system: user, agent, or service.
A scoped, on-behalf-of grant with containment.
Normative record: what happened, as whom, when.
Open a Conversation on a Deployment.
Upgrade to a new Session; lineage preserved.
Retire a Session; finish in-flight work.
Read Events as they append.
Append an Event to the active Session.
Federation-ready identity. Audit as a conformance requirement.
Scopes at every level, an IdP-agnostic Principal claims contract, and an on-behalf-of model with scope-pinned containment. “What did the agent do, as whom, when” is answerable by any conformant implementation — because AuditEvent is normative, not an add-on.
Identity & Audit →Three ways to conform. One kit to prove it.
All levels →Speaks OASP to a server: publish, send, stream, and follows migrations without dropping the thread.
Hosts Conversations & Sessions, implements migrate and drain, and MUST emit AuditEvents.
Bridges a non-OASP runtime into OASP, mapping native sessions onto OASP Sessions.
Loom is the reference. The standard invites the rest.
All implementations →Loom implements OASP. It is the production system OASP was extracted from — the standard is what Loom already had to be. Apache-2.0.
Build a Client, Server, or Adapter. Run the conformance kit. List your implementation here — the ecosystem is meant to be more than one vendor.
Start with the spec →