Personal agents, connected to companies
Personal Agent Protocol, also called Poppy, lets personal agents discover participating companies, sign users in when needed, and work through APIs, web pages or company agents. This guide follows draft 0.2. Version 0.1 is a separate older baseline.
The participants
A user delegates a task to their personal agent. A company publishes discovery metadata and capabilities. Work takes place in a Session at that company. The company can offer several execution paths; the personal agent selects from the capabilities actually advertised.
User → Personal Agent → Company discovery
↓
Session + authorization
↓
APIs / Web / Company AgentThis is a conceptual flow, not a requirement to implement every path. Optional features depend on the company’s metadata and supported extensions.
Sessions and accounts
A Session Token is a short-lived access credential. An Account Token represents the user’s approval for a personal agent to use an account and is an OAuth refresh token. Ending a session does not itself revoke account authorization. Keep session state, sign-in state and revocation separate.
Company developers can start with discovery and identity and an implementation path. Personal agent developers should also review credentials and retries. Field definitions and normative requirements belong to the official 0.2 specification.