release: 0.102.0

[kernel-internal]

Automated Release PR

0.102.0 (2026-09-14)

Features

• Accept a workload intent and use it to widen vendor coverage (39ffff8)
• Add guarded vault card fill operations (3927c96)
• Add single-use AgentCard prepare_checkout for Square (c439359)
• Allow replacing AgentCard cards after unknown creates (22a8731)
• Document punctuation key sequences (e7850fd)
• Honor managed auth browser regions (0fa2fa3)
• Reapply vendor guidance recommendations (dfcc7ec)
• Report proxy-restricted targets from config registry lookup (c276ebc)

---

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

---

Note

High Risk
Expands payment-adjacent vault operations (Square prepare_checkout, browser card fill) and changes perform_operation return typing, which can break callers expecting only VaultItem.

Overview
Release 0.102.0 bumps package version and syncs the Python SDK with expanded Kernel API surface—especially vault checkout automation, config registry workload analysis, and managed-auth browser regions.

Vault item operations are the largest behavioral change: client.vaults.items.perform_operation now returns VaultItemOperationResponse (updated item state or a value-free fill result) instead of always returning VaultItem. Typed overloads add prepare_checkout (single-use Square AgentCard preparation with checkout context) and fill (guarded Link-card field injection into a bound browser session). New models cover preparation lifecycle, fill field bindings/results, and richer AgentCard statuses; delete docs now allow abandoning certain recovery_required cards when no authorization ID was returned.

Config registry resolve accepts optional intent (HTTPS workload description). Lookup/resolve responses can include guidance markdown; resolve may also report workload_outcome. Lookup recommendation is typed as RecommendationResult (recommendation or structured no-recommendation).

Managed auth browser config gains optional region (us-east, eu-west, ap-southeast). Computer key press docs clarify X11 punctuation combos (e.g. Ctrl+minus, with Ctrl+- normalized).

Tests and api.md follow the new operation shapes and parameters.

^{Reviewed by Cursor Bugbot for commit 6143aa7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 1b95a4b. Configure here.}

[cursor]

Operation response union lacks discriminator

Medium Severity

VaultItemOperationResponse unions wallet, card, and fill-result models that all use a type field, but the alias is not annotated with a type discriminator. In the default loose client, any payload that fails strict validation is constructed as WalletVaultItem, so a fill result or card item can be returned as the wrong variant.

 

^{Reviewed by Cursor Bugbot for commit 1b95a4b. Configure here.}

[Sayan-]

yeet

[kernel-internal]

🤖 Release is at https://github.com/kernel/kernel-python-sdk/releases/tag/v0.102.0 🌻