{"version":"2.1.265","anchor":"onboarding-flow-adds-a-gateway-auth-path-condition-alongsi","canonical_anchor":"onboarding-flow-adds-a-gateway-auth-path-condition-alongsi","heading":"Onboarding flow adds a 'gateway' auth path condition alongside OAuth","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/onboarding-flow-adds-a-gateway-auth-path-condition-alongsi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Onboarding flow adds a 'gateway' auth path condition alongside OAuth\n\nOnboarding now also treats a 'gateway' authentication setup as equivalent to OAuth for its flow\n\n**Unclear.** Nothing has been read yet about how the `tengu_began_setup` or `tengu_onboarding_step` gates affect this on any account.\n\n**What**\n\nDuring onboarding, Claude Code previously decided whether to show the OAuth (the standard login-and-authorize flow) step based on one condition. It now also checks a second condition: whether the account is set up with a \"gateway\" authentication path. If so, that also feeds the same `oauthEnabled` telemetry field and affects whether the OAuth step is shown. A related preflight-skip condition was also adjusted.\n\n**Why**\n\nThis should make onboarding behave correctly for accounts using a gateway-based authentication setup, rather than only accounting for standard OAuth.\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}