release2026-06-112026-06-11

New features

Security: step-up verification, passkey management, and account recovery. Sensitive actions — sending funds, approving agent sessions, adding or removing passkeys — now require a quick passkey re-confirmation. Lost your passkey? You can now recover your account via email, with a one-click cancel link if it wasn't you. Passkey changes trigger email notifications, and your passkeys now show device names so you can tell them apart.
Sign-in and security history. Review recent sign-ins (time, location, device) and a log of all security verifications, so unfamiliar activity is easy to spot.
Protocol-agnostic session negotiation. Sessions can now be created and used regardless of which payment protocol a target service advertises. The session layer negotiates the protocol from the service response at runtime, so your agent code does not need to change when a service adds or changes payment protocols. This applies to both the CLI and the skills runtime.
Per-endpoint pricing in search results. The search tool now surfaces pricing details at the individual endpoint level. You can see the cost of each specific endpoint before making a request, rather than only seeing aggregate service-level pricing.
Agent feedback. Agents can now send feedback to us directly — reporting what worked, what didn't, and anything that got in their way — so we can spot rough edges and improve the platform faster.

Improvements

Correct user-agent headers on outbound requests. Both the CLI (kpass) and the search tool (ksearch) now send a properly identified user-agent header on all outbound HTTP requests, fixing request attribution on services that key on the user-agent for rate-limiting or analytics.
Quickstart paths and examples corrected. The quickstart guide now reflects current installation paths and removes stale code examples that would fail on a fresh install.
Skill loading optimized. The skills runtime now applies load-time optimization, reducing overhead for agents that use multiple skills.

Bundled ksearch binary is now locatable without repository access. In environments where the private repository is not accessible — such as CI pipelines, fresh installs, or contributor setups — the skills package previously failed to locate its bundled ksearch binary. It is now found via a relative path that does not require repository credentials.