AWP is a v0.1 draft. Propose changes through the RFD process.
The five primitives
Where to start
Read the specification
The normative v0.1 draft: transports, sessions, the loop, and safety.
Why AWP?
The gap it fills next to MCP, A2A, Gym, and ROS.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
AWP 0.1 is a draft. The SDKs, the reference world, and the conformance suite are in alpha.
AWP is an open protocol defining how an autonomous agent discovers, perceives, and acts within a world — virtual or physical.
| Primitive | What it is |
|---|---|
| World | An environment endpoint that advertises what can be perceived and done |
| Embodiment | The agent’s presence in the world — a robot body, avatar, cursor, camera rig |
| Observation | Typed, timestamped, multi-channel percepts |
| Action | A typed intent with a full lifecycle, not a fire-and-forget RPC |
| Session | The negotiated contract binding an agent to an embodiment, including safety grants |