Onboarding: capability-derived provider step and skip paths#550
Merged
Conversation
Self-hosted deployments with no model provider configured get a provider
step in the first-run wizard, between sign-in and the wizard proper: the
shared ProviderPicker (the exact /setup surface) in the wizard frame, with
its own always-visible "Skip for now". A save advances, refreshes the
setup-status cache, and kicks the Gmail profile scan; skipping defers the
scan entirely and the profile step degrades to a connect-a-model state
(no eternal spinner, no doomed "Try again"). Managed deployments never see
the step (ADR managed-deployment-mode.md).
The wizard's step sequence is now capability-derived and held by NAME
(onboardingSteps / OnboardingStep in lib.ts) — the provider step can join
the sequence after mount when the setup-status probe resolves, and a
numeric position could silently re-label the step the user is on. Sign-in
and the provider step are dotless prerequisites; the five product dots
stay stable for every deployment.
The sign-in step gains a quiet "Skip for now" (withheld when managed)
that completes onboarding minimally — PATCH {completed:true} plus the
browser timezone — so a user without a Google account still reaches the
app.
The proxy setup gate yields to an incomplete funnel: when unconfigured
and self-hosted it now probes GET /api/onboarding, and only an explicit
completed:false passes through (to /onboarding, whose provider step
replaces the /setup detour). Completed instances, unexpected payloads,
and failed probes keep the /setup bounce, and grandfathering keeps
existing installs out of the funnel. /setup invalidates the shared
setup-status cache on save so a funnel entered afterwards never shows a
spurious provider step.
useManagedMode's query is generalized to useSetupStatus (managed +
providerConfigured from the same probe); existing consumers unchanged.
Tests: step-sequence + needsProviderStep + profileCardView units,
StepProvider save/skip wiring, sign-in skip render/fire/pending, profile
connect-a-model state, proxy onboarding-probe decision table. ADR
web-onboarding-flow.md documents the capability-derived steps and skip
paths.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
onboardingSteps(withProviderStep)) so the capability-derived step can join the sequence without re-labeling progress dots; the five product dots stay deployment-stable.Test plan
bun run typecheck;bun run test— main 4803 pass / 0 fail, web 657 pass / 0 fail with coverage gate🤖 Generated with Claude Code