Document browserless 1Password access requests

[rgarcia]

Summary

KERNEL now creates 1Password access requests and reads their status from 1Password directly, so 1pw_create_access_request and 1pw_access_request_status no longer take a browser. SDK 0.121.0 (Node, Python, Go) removes browser_id from both operations, and the API rejects it. Only 1pw_fill uses the vault-attached browser and the 1Password extension.

Changes to the 1Password Agentic Autofill guide (vaults/1password.mdx):

• The setup steps for both OAuth paths say create and status need no browser, and you create a browser only to fill.
• The sequence diagram shows KERNEL calling 1Password for create and status, and loading the extension only for fill.
• The create and status code samples (TypeScript and Python) no longer create a browser or pass browser_id. The fill sample now creates the browser.
• Retry guidance: a provider_rejected 4xx means nothing was created and the request can be sent again. Only a 5xx or a network error is uncertain.
• The isolation limitation now applies to fills only.

No changelog entry, since it's written separately.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Oct 7, 2026, 8:10 PM

💡 Tip: Enable Automations to automatically generate PRs for you.