Version matrix and community implementations

Version matrix and community implementations

Official Poppy versions are frozen and independently addressable at /docs/{version}/spec. This page is a standalone English reference; it pairs with no Chinese page and carries no language alternates.

Official version matrix

0.1 / 0.20.30.41.0 (2026-11-14)
Sessionssingle token modelPoppy-Session header separates from OAuth; delegated keysper-request extensionsunchanged core, refinements
OAuthearly draftstandard token names; one sign-in covers multiple sessions—PAR may be required; ES256 + PS384; refresh keeps the same DPoP key
Scopespredefined read/writecompany-defined via auth.scopes; scope_hints—poppy:browser-sign-in is the only protocol scope
Versionssinglesinglesupported_versions / Poppy-Version negotiationunchanged
Browser join——one-time code via /authorize__Host- cookie; Mediated Sign-In retires 2027-03-17

Fields do not mix across rows: a 0.2 tutorial describing “session tokens” is describing a different protocol shape than 1.0’s two separate lines.

Community implementations, read as claims

ProjectClaimsVerified by this site
Community implementations tracking 0.4multiple declare 0.4 supportnot run — unknown
Implementations declaring a 1.0 draft (Nov 2026)author statements and harnessesnot run — unknown
Early 0.1 experimentsexplicitly 0.1not run — unknown

The rule this site follows: an author’s README is a claim, not a compatibility result. Until two implementations are run against each other at pinned revisions, the honest status is unknown, and that is what the table records.

What this site has actually run

The repository fixture fixtures/company-survey/ runs the official validator from the spec repository at commit 65618532:

  • the validator’s own test suite: 121/121 pass (node 22, 2026-11-16);
  • a read-only survey against a local HTTPS fixture serving a schema-valid poppy.json: the survey finds the document, reads protocol_version 1.0, the organization and the conversation endpoint, and reports no schema problems;
  • the same survey against an invalid variant (a conversation entry missing its required description) fails with discovery.schema naming the missing field.

That is static discovery conformance only. It does not run sign-in, sessions or revocation, and it does not verify any community implementation against any other. Rerun with sh fixtures/company-survey/run.sh.

Last updated on