Building on the Personal Agent Protocol Before 1.0: What Changed on 12 October, and How to Send Feedback

The Personal Agent Protocol (PAP, nicknamed Poppy) site at personalagentprotocol.org now says "Updated Oct 12, 2026". If you've built against draft 0.1, the short answer is that nothing you built needs to change. The specification, the operations extension and the guides read the same as before, and the draft is still 0.1.

What changed is everything around the spec: how the protocol gets to 1.0, how to send feedback, and who is involved.

What's new

• A Path to 1.0 page. Anyone can build against the draft. The authors are working through implementations with several design partners, and the spec will change based on what they learn. Until 1.0, a revision can break compatibility with earlier drafts.
• Renamed pages. "Overview" is now Introduction, and "Open topics" is now a section of Path to 1.0. The old URLs redirect, but update your links.
• A public partner list. Launch partners and design partners now sit in one list, grouped as personal agents (Instinct, Meta, OpenAI), companies and technology providers. No new names were added compared with the 9 October announcement.
• Contribution terms. Code and spec contributions are under Apache 2.0. Read the feedback clause before you send anything (more on that below).

How to give feedback

There are two routes. Both end with an email to [e-mail].

1. Inline comments. Turn on site commenting, select any text in the docs to comment on it, then export your comments from the "…" menu next to Comments.
2. An agent review. Download the "agent kit" from the Path to 1.0 page. It contains all the docs and an AGENTS.md that tells an agent how to write feedback in the form the authors want. Point your coding agent at it, review what it writes, and send it.

The authors say they most want feedback on:

• privacy and security: weaknesses in sign-in, sessions, tokens, permissions or how user data is handled;
• gaps: something you needed that the draft doesn't cover, or that doesn't work as written;
• simplification: parts that could be simpler without losing what they make possible;
• extensions many implementations need, "such as payments".

Read this before you send anything. Under the contribution terms, feedback you volunteer is licensed to "all other members and users of the protocol" on a "perpetual, irrevocable, nonexclusive, worldwide, royalty-free, sublicensable" basis, "without compensation". That's normal for a spec process. It means you shouldn't put anything in feedback that you want to keep for your own product.

What the draft still leaves out

The three open topics haven't changed:

• Payments: how a personal agent pays "in a way that fits the protocol, including how that works with existing payment protocols";
• Push notifications: how a company reaches the agent when no request is open;
• Attachments: receipts, return labels, images and forms in company messages.

If your agent needs to buy something today, the checkout still happens outside PAP. Some early adopters are already declaring payment details through their own extensions, and the authors list payments as an extension they'd welcome.

Who is building against the draft

Four days after draft 0.1, a handful of sites already serve a /.well-known/poppy.json. On PAP Checker's directory on 13 October, 10 sites publish one. Most are builders' demos and test benches, which is what you'd expect this early. Three are real businesses: Tilopay (payments, Costa Rica), Emora Health and Rent Our Bins. Each is a first mover on a protocol that's four days old.

None of the launch or design partners publish a poppy.json yet. The authors say they're working through implementations with partners first, so expect the first big names to appear alongside the reference implementation Sierra says is coming "over the next month".

What to watch next

• a public repository and named maintainers;
• the reference implementation;
• a JSON Schema or conformance suite;
• the first launch or design partner to publish poppy.json;
• a payments extension, and how it relates to existing payment protocols.

---

Disclosure: I maintain PAP Checker and UCP Checker. PAP Checker is an independent community checker, not affiliated with the protocol's authors. The draft is 0.1 and can change before 1.0.