Writing
Python SDK
Treeship and Python SDK.
Treeship 0.31: Verifiable Intent credentials, shipped
treeship vi implements the Verifiable Intent v0.1 draft, signs the Layer 3 pair with a Treeship receipt-chain attestation inside, and interoperates with the reference SDK both ways in CI.
The operator's yes, signed once
In Anthropic's commerce-agents reference, a merchant change applies only after a human approves it. treeship-commerce 0.29.0 makes that click a signed, single-use grant the apply receipt spends exactly once, on all three runtimes, with the console loop unchanged.
Receipts for agentic commerce
Anthropic's Claude Commerce Agents blueprint tells an agent what it may do in a store. Visa, Mastercard and Google are deciding how an agent may pay. Nobody in that stack keeps a record a stranger can check. Checked against a fresh clone.
You can't have agentic commerce without tamper-proof receipts
Anthropic's commerce-agents reference enforces its gates in code and leaves the record to the deployment. treeship-commerce is that record: every tool call signed on all three runtimes, the merchant's approval as a single-use grant, and a receipt for exactly the cart that went to checkout. Verifiable offline, wired by one command.
Treeship 0.25: revocation, and the wasm saga
Grant revocation works end to end and Linux arm64 binaries ship. It took four point releases to get a working verifier back onto npm, and the lesson is worth the telling.
Treeship 0.10.4: the audit hardening release
A keystore that claimed AES-GCM but was not, verifiers that trusted embedded keys, and a Merkle downgrade path. 0.10.3 and 0.10.4 close the audit findings and publish TS-2026-001.
Treeship 0.10.1: agent-native sharing and a supply-chain floor
An agent in a fresh sandbox can install Treeship, run a session, and return three working URLs. 0.10.1 hardens the binary, keystore, SDK, and MCP server underneath.
Treeship 0.7: session receipts you can verify offline
A closed session now becomes a .treeship package with a Merkle root, a static verifier page, a public hub URL, and A2A middleware.
Treeship 0.1: signed, content-addressed, verifiable offline
The first release put a DSSE signature on every agent action, named each artifact by its bytes, and let anyone check the result without a server.