Mark 1Password Agentic Autofill generally available

changelog.mdx

@@ -62,7 +62,7 @@ For API library updates, see the [Node SDK](https://github.com/onkernel/kernel-n
 
 ### Auth
 
-- Added **[1Password Agentic Autofill](/vaults/1password)** (preview). Your end users can approve access to logins that stay in their own 1Password account. Once your organization has preview access, connect accounts through the CLI, MCP server, or dashboard.
+- Added **[1Password Agentic Autofill](/vaults/1password)**. Your end users can approve access to logins that stay in their own 1Password account. Connect accounts through the CLI, MCP server, or dashboard.
 - The MCP server’s vault tools now return the API’s error codes and messages.
 - Added managed auth [reauthentication](/auth/configuration) controls to the dashboard: a **Health checks** switch and a separate toggle for automatic reauthentication. Both were already available through the API and CLI.
 - The dashboard now shows **Unverified** for managed auth connections whose health check was skipped because no check URL is set.

vaults/1password.mdx

@@ -3,8 +3,6 @@ title: "1Password Agentic Autofill"
 description: "Use 1Password Agentic Autofill in a KERNEL browser"
 ---
 
-**status:** <Badge color="yellow">preview</Badge>
-
 a vault-attached browser can get a login through one of two credential paths:
 
 1. **KERNEL-hosted collection** (`provider: "kernel"`): the user enters values in a KERNEL-hosted form, and your agent uses them through value-free bindings without seeing them.
@@ -35,7 +33,7 @@ KERNEL-hosted collection.
 | destination check | your controller authorizes the destination | the page must share the origin of an approved login |
 | supported logins | any fields you define | logins with a username, password, and one-time password, stored in the owner's own non-shared vault; no shared-vault items or passkeys |
 | totp | KERNEL generates codes from a stored seed | 1Password fills the login's stored one-time password; when the site asks for it on a later page, invoke `1pw_fill` again there |
-| availability | preview | preview |
+| availability | preview | generally available |
 
 neither path confirms that the website accepted the login. check the page after
 filling.

vaults/overview.mdx

@@ -76,7 +76,7 @@ backing for `fill` isn't currently available.
 | item backing | material path | availability |
 | --- | --- | --- |
 | KERNEL-backed credential | your trusted backend copies values from your source vault into the item | available today |
-| 1Password brokered approval | the user approves each request in the 1Password app, and the 1Password extension fills with `1pw_fill`; KERNEL stores no login values | preview |
+| 1Password brokered approval | the user approves each request in the 1Password app, and the 1Password extension fills with `1pw_fill`; KERNEL stores no login values | generally available |
 | third-party-backed credential | a provider connection supplies values to the item for `fill` | possible future model; not available today |
 | provider-backed card | a supported wallet provider supplies payment material to the item | available today |