Under the hood
Onboarding now also treats a 'gateway' authentication setup as equivalent to OAuth for its flow
What
During 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.
Why
This should make onboarding behave correctly for accounts using a gateway-based authentication setup, rather than only accounting for standard OAuth.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Nothing has been read yet about how the `tengu_began_setup` or `tengu_onboarding_step` gates affect this on any account.