Repository navigation
Conversation
…oes back Under MCP 2026-07-28 a server may answer tools/call with resultType "input_required" instead of acting; the client retries the same call under a new id. The guard took that answer for a success: it committed the reserved amount and marked any approval as used, then did both again on the retry. Now an input_required reply releases the hold with the reason execution.input-required, leaves the approval unspent, and the retry is decided on its own. Refusals carry resultType "complete" when the request named a protocol revision in _meta, so a 2026-07-28 client gets the shape it expects and an older client sees no change. Three tests, each shown to fail without the fix: the ledger ends with one released and one committed reservation and the daily headroom proves it; an approval survives the ask and is spent by the retry; a refusal carries resultType only for a client that announced the revision. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… the package The README opened with "verifiable, business-issued identity and authority". Identity for agents on the web is being standardised elsewhere (IETF Web Bot Auth, over HTTP Message Signatures) and its charter leaves authority out of scope, so the passport is now described as what it is: a business's signed statement of what its agents may commit, with Passport Guard enforcing that statement inside the business's own agents and receipts proving it. The package becomes @cubitrek/agent-passport. It carries the verifier, the signer, the guard, the Claude Code hook and the approvals tooling, so a name that said only "verifier" misdescribed it; it has not been published under either name. The /node subpath moves with it. "Agent passport" is a generic phrase with at least three other users, so the README now says which of them this is not, from their own pages. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #20 (same README and CHANGELOG files); merge that first and this diff shrinks to one commit.
Why
The README and spec opened with "verifiable, business-issued identity and authority". The IETF Web Bot Auth working group is standardising agent identity on the web over HTTP Message Signatures, with Cloudflare, Google, Visa and Mastercard built on it, and its charter leaves "what a bot may do" explicitly out of scope. So identity is somebody else's, and authority, the half this project actually defines, had no clear name for its enforcement side. "Agent passport" has also become a generic phrase (Trulioo, APort, ScopeBlind all use it).
What changes
@cubitrek/agent-passportreplaces@cubitrek/agent-passport-verifier(47 occurrences, including the/nodesubpath and the release workflow comment). Neither name has been published, so nothing breaks.npm pack --dry-runreports@cubitrek/agent-passport@0.1.2. The bareagent-passportnpm name belongs to someone else.@scopeblind/passportwithprotect-mcp, Web Bot Auth, and the site-sideagents.txtandagent-permissions.json, each described from its own page with a link, and says in one line how a passport differs. Plus one FAQ entry pointing at it.agent-passport guard --helpand the package README name Passport Guard; package keywords gainpassport-guard,spend-limits,human-in-the-loop,mcp-proxy,receipts.No code paths change. 138 tests, the execution-boundary harness and the end-to-end scenario are green.
Follow-ups that need Faizan's approval of exact copy (not in this PR)
tools/cubitrek-profiles/data.pyin growth-agent, which carries the canonical About copy.🤖 Generated with Claude Code