--- url: 'https://www.corbado.com/blog/chatgpt-atlas-passkeys' title: 'ChatGPT Atlas Passkeys Support' description: 'Explore ChatGPT Atlas passkey implementation: device-bound credentials, iCloud Keychain passkeys, AAGUID, QR code authentication. Technical breakdown & future outlook.' lang: 'en' author: 'Vincent Delitz' date: '2025-10-21T19:10:39.396Z' lastModified: '2026-03-27T07:01:49.885Z' keywords: 'ChatGPT Atlas passkeys, Atlas browser passkeys, ChatGPT Atlas authentication, Atlas passkey support, ChatGPT Atlas WebAuthn, Atlas browser security' category: 'Authentication' --- # ChatGPT Atlas Passkeys Support ### ChatGPT Atlas Passkey Support: Overview (January 2026) _Last updated: January 12, 2026_ | **Passkey Type** | **Support Status** | | :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | iCloud Keychain passkeys | ✅ **Supported** — save and use iCloud Keychain passkeys ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)) | | Device-bound passkeys (local profile) | ✅ **Supported** — **default option**; Atlas creates device-bound passkeys via its own authenticator (AAGUID `c3596e4b-b5a1-47ed-b979-0b4278368d1e`) | | Cross-device via QR code | ✅ **Supported** | | Security keys (e.g. YubiKeys) | ✅ **Supported** — external roaming authenticators work via WebAuthn | | 1Password browser extension | ✅ **Supported** — full autofill and passkey management ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes), [1Password blog](https://1password.com/blog/simplifying-credential-security-on-chatgpt-atlas)) | ## Timeline: ChatGPT Atlas Passkey Updates | **Icon** | **Date** | **Event** | **Description** | | :------- | :---------------- | :-------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 🚀 | October 21, 2025 | Atlas public launch | OpenAI releases ChatGPT Atlas browser with initial passkey support (device-bound only). | | 🔐 | October 28, 2025 | 1Password support | Atlas update enables 1Password native app connection. ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)) | | 🔑 | November 18, 2025 | iCloud Passkeys added | Atlas update adds iCloud Keychain passkey support: "Save and use iCloud keychain passkeys." ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)) | ## Key Facts - ChatGPT Atlas supports passkeys via device-bound credentials by default, with iCloud Keychain and 1Password integration and QR code cross-device authentication also available. - The **default device-bound** passkey in Atlas sets backupEligible to false, meaning it cannot sync across devices or to iCloud Keychain without choosing 'Save another way'. - Atlas uses a unique **AAGUID** (c3596e4b-b5a1-47ed-b979-0b4278368d1e) to identify its authenticator model, distinct from Chrome's AAGUID (adce0002-35bc-c60a-648b-0b25f1f05503). - **Google Password Manager** does not work in Atlas: it is built into Chrome and cannot be installed as an extension in a different browser. - **iCloud Keychain** passkey support was added November 18, 2025, roughly four weeks after Atlas's public launch on October 21, 2025. ## 1. Introduction: How well does ChatGPT Atlas support Passkeys? With [ChatGPT Atlas](https://openai.com/index/introducing-chatgpt-atlas/), OpenAI's new browser embedded with ChatGPT, users naturally wonder: **How well does ChatGPT Atlas support passkeys? Does it support platform passkeys and access to existing credential stores and password managers?** This article examines Atlas's passkey implementation, explores its technical characteristics and answers these critical questions about compatibility and limitations. **This article covers:** 1. **Platform passkey support and technical details** 2. **Atlas's unique AAGUID implementation** 3. **Cross-device authentication limitations** 4. **Future outlook and recommendations** ## 2. Platform Passkey Support: device-bound and iCloud Keychain ChatGPT Atlas supports creating platform passkeys through the WebAuthn API. Early Atlas builds produced **device-bound** credentials (as shown in the [attestation](https://www.corbado.com/glossary/attestation) below). However, Atlas has since added **iCloud Passkeys** support, allowing users to save and use **iCloud Keychain passkeys** in Atlas ([ChatGPT Atlas release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). **Important**: When creating a passkey, Atlas defaults to its local profile (device-bound). To save a passkey to [iCloud Keychain](https://www.corbado.com/glossary/icloud-keychain) instead, select **"Save another way"** during the [passkey creation](https://www.corbado.com/blog/passkey-creation-best-practices) flow: ![ChatGPT Atlas passkey creation dialog showing device-bound default with "Save another way" option to choose iCloud Keychain](https://s3.eu-central-1.amazonaws.com/corbado-cloud-staging-website-assets/atlas_save_another_way_3896e59aac.png) The dialog shows "This passkey will only be saved on this device" — confirming the default is device-bound. Click **"Save another way"** to select [iCloud Keychain](https://www.corbado.com/glossary/icloud-keychain) instead. ### 2.1 Technical Implementation When creating a passkey in Atlas, the authentication response reveals key characteristics. [View the complete passkey debugger result](https://www.passkeys-debugger.io/shared/6ec97608-c4a5-4351-8c18-ad41eba34b2a). The complete [attestation](https://www.corbado.com/glossary/attestation) response structure: ```json { "authenticatorAttachment": "platform", "id": "3WdZppEzL4aki7N5rYDZkN4AMebVxQKKCCw5-Nr48Kk", "rawId": "3WdZppEzL4aki7N5rYDZkN4AMebVxQKKCCw5-Nr48Kk", "response": { "attestationObject": "o2NmbXRmcGFja2VkZ2F0dFN0bXSiY2FsZyZjc2lnWEcwRQIgJqZ34SrRZDef5wwv9HivRVeBV1TbtXdSf02ZPlrFny4CIQDDp3nuUZc8iSlfjMd1U5ahTY6eFRIOn7a7H9SBg5Q-TWhhdXRoRGF0YVikPpZrl-Wqt-OFfBpyy2SraN1m7LT0GZORwGA7-6ujYkNFAAAAAMNZbku1oUftuXkLQng2jR4AIN1nWaaRMy-GpIuzea2A2ZDeADHm1cUCiggsOfja-PCppQECAyYgASFYIBvmw3MGkihD6xtMJGHGuVppqiyIBAwTceS3IZv7PtDSIlggHHerXJuTzxnMtVghblDP10UA-V9OhSGWDRsyoLfU6yE", "clientDataJSON": "eyJ0eXBlIjoid2ViYXV0aG4uY3JlYXRlIiwiY2hhbGxlbmdlIjoiVlFHME1EQkVFVEg4Q3NaZGd6ZVh5Wno4VGwwaGU0OWNKMENfYjlJQ3RGdyIsIm9yaWdpbiI6Imh0dHBzOi8vd3d3LnBhc3NrZXlzLWRlYnVnZ2VyLmlvIiwiY3Jvc3NPcmlnaW4iOmZhbHNlfQ", "transports": ["internal"], "authenticatorData": "PpZrl-Wqt-OFfBpyy2SraN1m7LT0GZORwGA7-6ujYkNFAAAAAMNZbku1oUftuXkLQng2jR4AIN1nWaaRMy-GpIuzea2A2ZDeADHm1cUCiggsOfja-PCppQECAyYgASFYIBvmw3MGkihD6xtMJGHGuVppqiyIBAwTceS3IZv7PtDSIlggHHerXJuTzxnMtVghblDP10UA-V9OhSGWDRsyoLfU6yE", "publicKey": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEG-bDcwaSKEPrG0wkYca5WmmqLIgEDBNx5Lchm_s-0NIcd6tcm5PPGcy1WCFuUM_XRQD5X06FIZYNGzKgt9TrIQ", "publicKeyAlgorithm": -7 }, "type": "public-key", "clientExtensionResults": {} } ``` Key fields from the [attestation](https://www.corbado.com/glossary/attestation) response: **Authenticator Attachment**: `"authenticatorAttachment": "platform"` indicates the passkey uses a [platform authenticator](https://www.corbado.com/glossary/platform-authenticator) (built-in). Whether it’s device-bound or synced depends on the [passkey provider](https://www.corbado.com/blog/passkey-providers) and backup flags. **Transport**: `"transports": ["internal"]` indicates the credential is stored in a [platform authenticator](https://www.corbado.com/glossary/platform-authenticator). This does not, by itself, tell you whether the passkey can sync. **Credential ID**: `"id": "3WdZppEzL4aki7N5rYDZkN4AMebVxQKKCCw5-Nr48Kk"` uniquely identifies this passkey but provides no link to external credential stores. The parsed attestation response reveals additional details: ```json { "authenticatorAttachment": "platform", "id": "3WdZppEzL4aki7N5rYDZkN4AMebVxQKKCCw5-Nr48Kk", "rawId": "3WdZppEzL4aki7N5rYDZkN4AMebVxQKKCCw5-Nr48Kk", "response": { "attestationObject": { "fmt": "packed", "attStmt": { "alg": "ES256 (-7)", "sig": "MEUCICamd-Eq0WQ3n-cML_R4r0VXgVdU27V3Un9NmT5axZ8uAiEAw6d57lGXPIkpX4zHdVOWoU2OnhUSDp-2ux_UgYOUPk0" }, "authData": { "rpIdHash": "PpZrl-Wqt-OFfBpyy2SraN1m7LT0GZORwGA7-6ujYkM", "flags": { "userPresent": true, "userVerified": true, "backupEligible": false, "backupStatus": false, "attestedData": true, "extensionData": false }, "counter": 0, "aaguid": { "raw": "c3596e4b-b5a1-47ed-b979-0b4278368d1e", "name": "Unknown" }, "credentialID": "3WdZppEzL4aki7N5rYDZkN4AMebVxQKKCCw5-Nr48Kk", "credentialPublicKey": "pQECAyYgASFYIBvmw3MGkihD6xtMJGHGuVppqiyIBAwTceS3IZv7PtDSIlggHHerXJuTzxnMtVghblDP10UA-V9OhSGWDRsyoLfU6yE", "parsedCredentialPublicKey": { "keyType": "EC2 (2)", "algorithm": "ES256 (-7)", "curve": 1, "x": "G-bDcwaSKEPrG0wkYca5WmmqLIgEDBNx5Lchm_s-0NI", "y": "HHerXJuTzxnMtVghblDP10UA-V9OhSGWDRsyoLfU6yE" } } }, "clientDataJSON": { "type": "webauthn.create", "challenge": "VQG0MDBEETH8CsZdgzeXyZz8Tl0he49cJ0C_b9ICtFw", "origin": "https://www.passkeys-debugger.io", "crossOrigin": false }, "transports": ["internal"], "authenticatorData": "PpZrl-Wqt-OFfBpyy2SraN1m7LT0GZORwGA7-6ujYkNFAAAAAMNZbku1oUftuXkLQng2jR4AIN1nWaaRMy-GpIuzea2A2ZDeADHm1cUCiggsOfja-PCppQECAyYgASFYIBvmw3MGkihD6xtMJGHGuVppqiyIBAwTceS3IZv7PtDSIlggHHerXJuTzxnMtVghblDP10UA-V9OhSGWDRsyoLfU6yE", "publicKey": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEG-bDcwaSKEPrG0wkYca5WmmqLIgEDBNx5Lchm_s-0NIcd6tcm5PPGcy1WCFuUM_XRQD5X06FIZYNGzKgt9TrIQ", "publicKeyAlgorithm": -7 }, "type": "public-key", "clientExtensionResults": {} } ``` Notable parsed values: `"backupEligible": false` and `"backupStatus": false` indicate this credential is not backup-eligible and is not backed up (i.e., device-bound). The [AAGUID](https://www.corbado.com/glossary/aaguid) is `"raw": "c3596e4b-b5a1-47ed-b979-0b4278368d1e"`. Atlas's [client capabilities](https://www.corbado.com/blog/webauthn-client-capabilities) show broad WebAuthn feature support: ```json { "conditionalCreate": true, "conditionalGet": true, "extension:appid": true, "extension:appidExclude": true, "extension:credBlob": true, "extension:credProps": true, "extension:credentialProtectionPolicy": true, "extension:enforceCredentialProtectionPolicy": true, "extension:getCredBlob": true, "extension:hmacCreateSecret": true, "extension:largeBlob": true, "extension:minPinLength": true, "extension:payment": true, "extension:prf": true, "hybridTransport": true, "passkeyPlatformAuthenticator": true, "relatedOrigins": true, "signalAllAcceptedCredentials": true, "signalCurrentUserDetails": true, "signalUnknownCredential": true, "userVerifyingPlatformAuthenticator": true } ``` Despite comprehensive WebAuthn capability support (including `"hybridTransport": true` for [QR code](https://www.corbado.com/blog/qr-code-login-authentication) authentication), device-bound credentials limit practical usability. ### 2.2 What this means for Users The passkey shown above is device-bound. If you [create a passkey](https://www.corbado.com/blog/passkey-creation-best-practices) in Atlas and it is not backup-eligible (e.g. `"backupEligible": false`), that passkey exists **only** on that device. You cannot: - Access it from another device - Sync it via [iCloud Keychain](https://www.corbado.com/glossary/icloud-keychain) - Transfer it to another browser Separately, Atlas can also save and use **iCloud Keychain passkeys**, which _do_ sync across your Apple devices ([ChatGPT Atlas release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). To use iCloud Keychain, choose **"Save another way"** when prompted — the default saves to Atlas's local profile. ## 3. Atlas's unique AAGUID: a new Authenticator Identity ChatGPT Atlas introduces a new [Authenticator Attestation Global Unique Identifier](https://www.corbado.com/glossary/aaguid) (AAGUID): `c3596e4b-b5a1-47ed-b979-0b4278368d1e`. ### 3.1 Understanding AAGUIDs The [AAGUID](https://www.corbado.com/glossary/aaguid) is a 128-bit identifier that indicates the [authenticator](https://www.corbado.com/glossary/authenticator) model. This identifier appears in the `authenticatorData` (specifically in the `attestationObject`) during [passkey creation](https://www.corbado.com/blog/passkey-creation-best-practices), allowing websites to determine what type of [authenticator](https://www.corbado.com/glossary/authenticator) created the credential. For comparison, [Chrome on Mac](https://www.corbado.com/glossary/chrome-on-mac) uses: `adce0002-35bc-c60a-648b-0b25f1f05503` Atlas's unique [AAGUID](https://www.corbado.com/glossary/aaguid) indicates a distinct [authenticator](https://www.corbado.com/glossary/authenticator) implementation. However, an AAGUID is simply an identifier for the authenticator model (it does **not** define sync or credential-store integration behavior) ([FIDO AAGUID definition](https://fidoalliance.org/specs/fido-v2.0-rd-20180227/fido-client-to-authenticator-protocol-v2.0-rd-20180227.html#authenticator-attestation-guid-aaguid), [WebAuthn authenticator data](https://www.w3.org/TR/webauthn-2/#authenticator-data)). ### 3.2 Implications of a distinct AAGUID Atlas having its own AAGUID does not, by itself, mean Atlas is (or will remain) isolated from external credential stores. Sync and interoperability are product decisions that can change over time. **Historical Context**: Some ecosystems started with device-bound credentials and later added syncing. Atlas similarly shipped with device-bound credentials (see `"backupEligible": false` above) and later added iCloud Keychain passkey support ([ChatGPT Atlas release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). ## 4. Cross-Device Authentication: expect more QR Codes While Atlas supports WebAuthn's cross-device authentication flow, the experience differs significantly from cloud-[synced passkey](https://www.corbado.com/blog/device-bound-synced-passkeys) ecosystems. ### 4.1 How Cross-Device Authentication works **QR Code Flow**: When accessing a website that requires authentication: 1. Atlas displays a [QR code](https://www.corbado.com/blog/qr-code-login-authentication) on the screen 2. You scan it with your mobile phone 3. Your phone (with its own passkeys stored in e.g. iCloud Keychain) completes the authentication 4. The session is established on your Atlas browser **Practical Impact**: This works but adds friction when your passkeys live in a synced provider that Atlas does not directly integrate with. On Apple devices, Atlas can save and use **iCloud Keychain passkeys** directly ([ChatGPT Atlas release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). ### 4.2 Passkey Accessibility across Devices **Passkeys stored in iCloud Keychain**: Atlas can save and use iCloud Keychain passkeys directly ([ChatGPT Atlas release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). **Logging in to Google**: Basic authentication to Google services works in Atlas (via OAuth / OIDC), but don't expect the seamless passkey experience you get in Chrome or Safari where your credentials are readily available. ## 5. Future Outlook: Passkeys for OpenAI Agents? The current limitations suggest Atlas's passkey implementation is in its early stages. Several developments seem likely: **Synchronization**: OpenAI may eventually enable passkey synchronization across Atlas installations, similar to how other browsers evolved from device-bound to synced passkeys. **Password Manager Integration**: [1Password](https://www.corbado.com/blog/1password-passkeys-best-practices-analysis) already supports Atlas via browser extension ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). Other password managers (Bitwarden, [Dashlane](https://www.corbado.com/blog/dashlane-passkeys), etc.) may follow. **OpenAI Agent Access**: A compelling possibility is that OpenAI could make Atlas passkeys accessible to OpenAI agents. Imagine AI assistants that can authenticate on your behalf using securely managed passkeys - a natural extension of OpenAI's broader agent vision. This could enable agents to perform authenticated actions across services while maintaining security through passkey-based authentication. ## 6. Conclusion: answering the Key Questions ChatGPT Atlas represents OpenAI's ambitious entry into the browser space, but its passkey implementation remains limited. Let's answer the questions posed at the beginning: ### 6.1 How well does ChatGPT Atlas support passkeys? Atlas supports passkeys, including **device-bound platform passkeys** (as shown in the attestation above) and **iCloud Keychain passkeys** ([ChatGPT Atlas release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). The implementation uses WebAuthn correctly, but capabilities depend on which passkey provider you use. ### 6.2 Does ChatGPT Atlas support platform passkeys? **Yes**, Atlas supports platform passkeys. The `"authenticatorAttachment": "platform"` parameter and `"transports": ["internal"]` confirm that passkeys are created using a [platform authenticator](https://www.corbado.com/glossary/platform-authenticator). Whether a passkey is device-bound or synced depends on the [passkey provider](https://www.corbado.com/blog/passkey-providers) (e.g. Atlas device-bound vs iCloud Keychain). ### 6.3 Does ChatGPT Atlas support security keys like YubiKeys? **Yes**, Atlas supports external security keys (roaming [authenticators](https://www.corbado.com/glossary/authenticator)) such as [YubiKeys](https://www.corbado.com/glossary/yubikey). The WebAuthn implementation in Atlas handles both platform [authenticators](https://www.corbado.com/glossary/authenticator) and roaming [authenticators](https://www.corbado.com/glossary/authenticator). You can register and authenticate with a hardware [security key](https://www.corbado.com/glossary/security-key) connected via USB, NFC, or Bluetooth. ### 6.4 Does ChatGPT Atlas access existing credential stores and password managers? **Yes**, Atlas integrates with: - **iCloud Keychain**: Save and use iCloud Keychain passkeys ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)) - **1Password**: Full browser extension support with autofill and passkey management ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes), [1Password blog](https://1password.com/blog/simplifying-credential-security-on-chatgpt-atlas)) Note: **Google Password Manager** does not work in Atlas — it's built into Chrome and cannot be installed as an extension. For passkeys stored there, use [QR code](https://www.corbado.com/blog/qr-code-login-authentication)-based cross-device authentication. Atlas's unique AAGUID (`c3596e4b-b5a1-47ed-b979-0b4278368d1e`) identifies the authenticator model; it does not determine credential-store integration ([FIDO spec](https://fidoalliance.org/specs/fido-v2.0-rd-20180227/fido-client-to-authenticator-protocol-v2.0-rd-20180227.html#authenticator-attestation-guid-aaguid)). ### 6.5 Recommendations **Do**: - **Use iCloud Keychain**: Select **"Save another way"** when creating passkeys to sync across your Apple devices. - **Install 1Password**: The [1Password](https://www.corbado.com/blog/1password-passkeys-best-practices-analysis) browser extension works in Atlas with full autofill and passkey support ([release notes](https://help.openai.com/en/articles/12591856-chatgpt-atlas-release-notes)). - **Use QR codes**: For passkeys stored in providers without Atlas extensions (e.g. Google [Password Manager](https://www.corbado.com/blog/passkeys-vs-password-managers), [Bitwarden](https://www.corbado.com/blog/passkey-analysis-bitwarden-developer-survey-2024)), use QR code-based cross-device authentication. **Don't**: - **Rely on defaults**: Avoid [device-bound passkeys](https://www.corbado.com/faq/are-passkeys-device-specific) (the default) if you need multi-device access. - **Expect Google Password Manager**: It's built into Chrome and cannot be installed in Atlas — use QR codes instead. ### 6.6 What this means For now, Atlas passkeys are best avoided for critical accounts. The infrastructure exists but lacks the polish and integration of mature passkey implementations in Chrome, Safari or Edge. As OpenAI develops Atlas, expect these capabilities to evolve - particularly if they pursue the vision of agent-accessible authentication. **Best Approach**: Continue using established browsers and password managers for critical authentication while monitoring Atlas's evolution. When (and if) OpenAI enhances passkey support, the foundation they're building today will become more useful. ## Frequently Asked Questions ### How do I save a passkey to iCloud Keychain in ChatGPT Atlas instead of to the device? Atlas defaults to saving device-bound passkeys (backupEligible: false) that exist only on one device and cannot sync. To save to iCloud Keychain instead, select 'Save another way' during the passkey creation flow. iCloud Keychain support was added in the November 18, 2025 Atlas update. ### What is ChatGPT Atlas's AAGUID and does it affect which password managers can integrate with it? Atlas uses AAGUID c3596e4b-b5a1-47ed-b979-0b4278368d1e, a unique 128-bit identifier for its authenticator model. The AAGUID identifies the authenticator type but does not control credential-store integration. 1Password supports Atlas via browser extension with full autofill and passkey management, added in the October 28, 2025 update. ### Why doesn't Google Password Manager work in ChatGPT Atlas and how can I use those passkeys? Google Password Manager is built into Chrome and cannot be installed as an extension in Atlas. For passkeys stored in Google Password Manager, use QR code cross-device authentication: Atlas displays a QR code, you scan it with your phone and your phone completes the authentication using its stored credentials. ### What passkey capabilities did ChatGPT Atlas launch with versus what it supports now? At public launch on October 21, 2025, Atlas supported device-bound passkeys only. 1Password browser extension support arrived October 28, 2025 and iCloud Keychain passkey support was added November 18, 2025. Security keys such as YubiKeys work via Atlas's WebAuthn implementation across all versions.