Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/examples.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -59,9 +59,9 @@ jobs:
# to have no upper bound. The ref is the Agent Runtimes branch that adopts the new
# SDK.
#
# 0.37 breaks the API: Agent Runtimes adopts it on feat/scenes (pin >=0.37.0,<0.38), so
# the job installs Agent Runtimes from that branch until a release accepts 0.37.
AGENT_RUNTIMES_REF: feat/scenes
# Empty: Agent Runtimes 1.6.83 accepts 0.37 (personal-agent-protocol >=0.37.0,<0.38),
# so the job tests the released package.
AGENT_RUNTIMES_REF: ''
steps:
- uses: actions/checkout@v6
- uses: astral-sh/setup-uv@v7
Expand Down
27 changes: 27 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,33 @@

# Changelog

## 0.37.1 (2026-11-17)

Fixes from the review of 0.37.0, in both SDKs. No API change.

- **A bound refresh token keeps its sign-in at a Bearer-only MCP server** (spec 4.4, 4.5, 7).
`token_for_mcp` (`tokenForMcp`) replaced the issuer's DPoP algorithms with the server's, so
for a server that takes only Bearer the refresh went without a proof; a company that binds
refresh tokens answered `invalid_grant` and the refresh token was deleted. The refresh now
proves with the refresh token's key whenever the issuer lists ES256, and the reference
companies give a server whose metadata lists no DPoP algorithm a Bearer token even after a
proof. The conformance case `dpop.mcp-server-decides-the-proof` checks the token type the
server takes.
- **`open_link` no longer takes the callback state** (spec 4.2). The link has its own record, a
copy of the request, so a link reopened while the redirect is being completed can't make
`complete` fail; `complete` alone consumes the state, and drops the link with it.
- **`effectiveContext`** (TypeScript) defines each field as an own property: a context field
named `__proto__` is a field, never the object's prototype. Python's dict had no such issue.
- **An empty SSE `event:` name** is the default `message` event, never skipped as unknown
(spec 8.6).
- **Conformance**: `dpop.pushed-authorization-request` requires an explicit OAuth refusal (an
error response, or a redirect with `error`) for a request that wasn't pushed; a redirect to a
login page no longer passes.
- CI: the Examples job tests the released Agent Runtimes again (1.6.83 accepts 0.37):
`AGENT_RUNTIMES_REF` emptied.
- Python 3.10: the RSA key-size check reads the modulus with an explicit byte order (fixed
before the 0.37.0 tag; the 3.10 CI job runs the PS384 tests).

## 0.37.0 (2026-11-17)

Version 1.0 **as published** (upstream `8c02b42`, frozen 2026-11-14; reviewed through
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/protocol/conformance-report.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: Compatibility and conformance report

# Compatibility and conformance report

SDK version **0.37.0**, PAP profile **0.4** (as published 2026-11-10), Operations extension **v3**; the pairings run at protocol version **1.0**, the default (1.0 as published 2026-11-14); the suite also runs at 0.4 in every pairing. Each pairing runs every positive, negative and recovery fixture case over real TCP and TLS, the personal agent in one language and the reference company (Manzanita) in the other. A case is skipped, never passed, when a side lacks what it needs; the reason is listed below.
SDK version **0.37.1**, PAP profile **0.4** (as published 2026-11-10), Operations extension **v3**; the pairings run at protocol version **1.0**, the default (1.0 as published 2026-11-14); the suite also runs at 0.4 in every pairing. Each pairing runs every positive, negative and recovery fixture case over real TCP and TLS, the personal agent in one language and the reference company (Manzanita) in the other. A case is skipped, never passed, when a side lacks what it needs; the reason is listed below.

## Pairings

Expand Down
2 changes: 1 addition & 1 deletion docs/docs/protocol/coverage/operational-guidance.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ The Guides' recommendations (SHOULD), kept apart from the specification. Upstrea
| `GUIDE-co-session-05` | Verifying the Session header | SHOULD | company | Rejecting a reused jti is optional, as it is for DPoP proofs. | [`verify_session_jwt`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/verify.py)<br/>[`CompanyService._caller`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`StoreReplayCache`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/points.py) | [`test_delegated_keys.py::test_a_session_jwt_has_the_specs_header_and_claims`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_delegated_keys.py)<br/>[`test_security_review.py::test_a_copied_access_token_is_worth_nothing_without_the_agents_session_jwt`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_security_review.py)<br/>[`test_conformance.py::test_python_agent_python_company_over_tls`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_conformance.py)<br/>[`test_company_refusals.py::test_a_replayed_token_request_is_refused`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_company_refusals.py)<br/>`security.session-jwt-replay` | implemented |
| `GUIDE-co-session-06` | Verifying the Session header | SHOULD | company | Binding access tokens with DPoP is your choice (4.5). If you do, verify the proof as RFC 9449 describes, separately from the Session JWT. | [`verify_dpop_proof`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/verify.py)<br/>[`CompanyConfig`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`CompanyService._caller`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py) | [`test_dpop.py::test_optional_binds_with_a_proof_and_issues_bearer_without`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_dpop.py)<br/>[`test_dpop.py::test_a_refused_proof_spends_no_device_code`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_dpop.py)<br/>[`test_conformance.py::test_python_agent_python_company_binding_with_dpop_over_tls`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_conformance.py)<br/>`dpop.metadata-lists-es256`<br/>`dpop.token-bound-and-used`<br/>`dpop.token-request-needs-a-proof`<br/>`dpop.token-proof-for-another-url`<br/>`dpop.token-proof-with-ath`<br/>`dpop.token-proof-outside-the-window`<br/>`dpop.token-proof-wrong-typ`<br/>`dpop.nonce-at-the-token-endpoint`<br/>`dpop.nonce-at-a-resource`<br/>`dpop.bound-token-without-a-proof`<br/>`dpop.bound-token-as-bearer`<br/>`dpop.proof-of-another-key`<br/>`dpop.proof-replayed`<br/>`dpop.proof-wrong-ath`<br/>`dpop.proof-wrong-htm`<br/>`dpop.proof-wrong-htu`<br/>`dpop.proof-outside-the-window`<br/>`dpop.session-header-still-checked`<br/>`dpop.conversation-and-stream`<br/>`dpop.feedback`<br/>`dpop.browser-join`<br/>`dpop.mcp-token-bound`<br/>`dpop.mcp-challenge-keeps-resource-metadata`<br/>`dpop.mcp-challenges-bearer-then-dpop` | implemented |
| `GUIDE-co-session-07` | Verifying the Session header | SHOULD | company | Session records need not be durable; conversations are separate records that can outlast the session that started them. Behind a load balancer, share session state across the servers that handle it, as with server-side cookie sessions, so requests reach the same state whichever server handles them. | [`CompanyStore`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/store.py) | [`test_company_store.py::test_a_company_restarted_over_its_store_continues_every_flow`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_company_store.py)<br/>[`test_security_review.py::test_finding_4_a_session_jwt_replayed_at_another_replica_is_refused`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_security_review.py) | implemented |
| `GUIDE-mcp-01` | MCP and UCP interoperability | SHOULD | both | Use Bearer tokens for ordinary MCP authorization. Use DPoP only with a server that advertises it and a client that supports it (section 7): the issuer that requires a proof still lets ordinary MCP clients get a Bearer token for an MCP resource. | [`RefreshTokenClient.token_for_mcp`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/accounts.py)<br/>[`ServiceTokens.token_for`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/accounts.py)<br/>[`CompanyService.protected_resource_metadata`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`CompanyService._token_binding`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`CompanyConfig.mcp_token_schemes`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py) | [`test_fixtures.py::test_local_fixture_case`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_fixtures.py)<br/>[`test_conformance.py::test_python_agent_python_company_binding_with_dpop_over_tls`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_conformance.py)<br/>`dpop.mcp-proof-from-the-servers-metadata`<br/>`dpop.mcp-metadata-lists-es256`<br/>`dpop.mcp-challenges-bearer-then-dpop`<br/>`dpop.mcp-bearer-without-a-proof`<br/>`dpop.mcp-server-decides-the-proof` | implemented |
| `GUIDE-mcp-01` | MCP and UCP interoperability | SHOULD | both | Use Bearer tokens for ordinary MCP authorization. Use DPoP only with a server that advertises it and a client that supports it (section 7): the issuer that requires a proof still lets ordinary MCP clients get a Bearer token for an MCP resource. | [`RefreshTokenClient.token_for_mcp`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/accounts.py)<br/>[`ServiceTokens.token_for`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/accounts.py)<br/>[`CompanyService.protected_resource_metadata`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`CompanyService._token_binding`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`CompanyConfig.mcp_token_schemes`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py)<br/>[`CompanyService._takes_dpop`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/company/service.py) | [`test_fixtures.py::test_local_fixture_case`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_fixtures.py)<br/>[`test_conformance.py::test_python_agent_python_company_binding_with_dpop_over_tls`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_conformance.py)<br/>`dpop.mcp-proof-from-the-servers-metadata`<br/>`dpop.mcp-metadata-lists-es256`<br/>`dpop.mcp-challenges-bearer-then-dpop`<br/>`dpop.mcp-bearer-without-a-proof`<br/>`dpop.mcp-server-decides-the-proof` | implemented |
| `GUIDE-pa-ids-05` | User IDs | SHOULD | personal-agent | When adding or changing an issuer changes the Company's identifier, use new user IDs, agent IDs, delegated keys, and sessions. Do not fall back to the domain because issuer discovery failed. | [`DiscoveredCompany.identifier`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/models.py)<br/>[`DiscoveryClient.discover`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/discovery.py) | [`test_issuerless.py::test_a_known_issuer_is_never_lost_to_an_error`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_issuerless.py) | implemented |
| `GUIDE-pa-access-01` | Planning account access | SHOULD | personal-agent | A conversation entry's access: signed_in hints that it needs account access from the start; without that hint, start signed out and respond to challenges or authorization events. | [`AgentProtocol.account_access`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/models.py) | [`test_fixtures.py::test_local_fixture_case`](https://github.com/datalayer/personal-agent-protocol/blob/main/personal_agent_protocol/__tests__/test_fixtures.py) | **partial**: The SDK reads the hint (account_access); when to sign in is the host's. |
| `GUIDE-co-web-cookie-01` | Browser sessions | SHOULD | company | Use a cookie for the session that's separate from your login cookie, and check it first. After a signed-out join, keep the browser's login cookie. After a signed-in join, clear it, so the browser is signed out when the session's sign-in ends. | — | — | **not-applicable**: The reference companies have no website login beyond the Session's cookie, which a later join replaces. |
Expand Down
3 changes: 2 additions & 1 deletion docs/docs/releases/compatibility.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Compatibility

# Compatibility

This page is versioned with the SDK: it describes **SDK 0.37.0**.
This page is versioned with the SDK: it describes **SDK 0.37.1**.

## The PAP version implemented

Expand Down Expand Up @@ -35,6 +35,7 @@ profile, never picked up from an unattended fetch.

| SDK (PyPI and npm) | PAP profile | Specification revision | Operations | Breaking changes |
| --- | --- | --- | --- | --- |
| `0.37.1` | `0.4` | 2026-11-10 | v3 | none: a bound refresh token keeps its sign-in at a Bearer-only MCP server, `open_link` leaves the callback state to `complete`, an empty SSE event name is a message, and `effectiveContext` keeps a `__proto__` field as a field |
| `0.37.0` | `0.4` | 2026-11-10 | v3 | [0.36 → 0.37](/releases/migration/#036--037): 1.0 as published (`8c02b42`): required conversation protocol descriptions (`agent_description`), Pushed Authorization Requests, `prompt=consent`, refresh tokens bound to their DPoP key, ports in `organization.domain`, one sign-in for every resource, and unknown values read safely |
| `0.36.1` | `0.4` | 2026-11-10 | v3 | none: a Session persisted without its version (before 0.36) restores at 0.4 in TypeScript too, as in Python |
| `0.36.0` | `0.4` | 2026-11-10 | v3 | [0.35 → 0.36](/releases/migration/#035--036): the 1.0 draft is the default in both SDKs and both reference companies; 0.4 is used only when named (`protocol_versions`) |
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@datalayer/personal-agent-protocol",
"version": "0.37.0",
"version": "0.37.1",
"description": "TypeScript SDK for Personal Agent Protocol 0.4 (2026-11-10) and its Operations extension v3",
"repository": {
"type": "git",
Expand Down
Loading
Loading