Orchestration
Personal Agent Protocol Ships a Draft — and a Guest List With a Notable Absence
On October 9, Sierra published a draft specification for the Personal Agent Protocol, the open standard it announced three days earlier with Meta, Shopify, Stripe, Walmart and others. The draft, nicknamed Poppy, came with a much longer partner list than the original announcement: Sierra added 35 design partners, OpenAI among them, while Anthropic is not listed.
The protocol's job is narrow but real. Sessions are built on OAuth: an agent can start as a guest to check stock or a return policy, and once a customer signs in, the business decides whether that agent gets read-only or write access. That session then carries across channels, so a question asked before sign-in and an order changed after it belong to the same visit rather than two disconnected interactions. Critically, the business — not the agent framework — decides whether a personal agent reaches it through a website, through APIs using standards like MCP and OpenAPI, or through an agent of its own. That's the orchestration layer: Poppy doesn't tell agents how to think, it tells them which door to use and what they're allowed to carry through it.
The partner list matters here almost as much as the spec. Stripe and Shopify are also partners in a rival agentic-commerce protocol run by Visa, meaning the biggest payment rails in agent commerce are currently hedging across at least two competing standards rather than consolidating on one. OpenAI's addition to the design-partner roster gives Poppy a major model provider's weight, but Anthropic's absence is conspicuous given how central Claude-based agents have become in enterprise deployments — it suggests the standard isn't yet neutral ground, just broadly attended ground.
The timeline is tight: a v0.1 specification and reference implementation are due by the end of October, which is fast for a multi-vendor standard touching authentication, payments-adjacent plumbing, and channel routing across companies the size of Walmart and Meta. Draft status also means none of this is binding yet — the session model, the read/write access tiers, the channel-selection logic are all proposals a business could still push back on before implementation.
What's genuinely new since the initial announcement isn't the concept — personal agents authenticating to businesses — but the fact that a working draft now exists with concrete mechanics (OAuth sessions, cross-channel continuity, business-controlled channel choice) rather than just a joint press statement. Protocols live or die on whether the draft survives contact with 35 companies' actual integration requirements, and that process is only now starting.