Skip to content

fix: make Skip setup button actually skip onboarding and setup#2083

Draft
posthog[bot] wants to merge 2 commits intomainfrom
posthog-code/fix-skip-setup-button
Draft

fix: make Skip setup button actually skip onboarding and setup#2083
posthog[bot] wants to merge 2 commits intomainfrom
posthog-code/fix-skip-setup-button

Conversation

@posthog
Copy link
Copy Markdown
Contributor

@posthog posthog Bot commented May 7, 2026

Summary

The dev-only Skip setup button in the onboarding flow didn't actually skip anything — it called navigateToSetup() (which routes to the setup view) and only flipped hasCompletedOnboarding. App.tsx then bounced the user back to <OnboardingFlow /> because of a !selectedDirectory guard that existed solely to paper over this broken state.

Now:

  • New handleSkip calls completeOnboarding() + completeSetup() and navigates to task-input (the home view), so the button actually skips both onboarding and the setup view.
  • The IS_DEV gate is removed, so the button is available in production too (per the request).
  • The !selectedDirectory guard in App.tsx is dropped — TaskInput already handles an empty selectedDirectory by auto-populating from mostRecentRepo and exposing a folder picker.
  • The existing handleComplete (used by SignalsStep for the normal happy-path completion) is unchanged, so the regular flow still routes through SetupView.

Test plan

  • In dev: launch a fresh state (localStorage.clear()), click Skip setup on the welcome screen → land on the main app's task-input view, no bounce back to onboarding.
  • In dev: pick a directory, click Skip setup mid-flow → same result, with the picked directory preserved.
  • In prod build: the button is visible in the onboarding footer and behaves the same.
  • Normal happy path through SignalsStep still routes to <SetupView /> (unchanged).

Created with PostHog Code

PostHog Code added 2 commits May 7, 2026 11:49
The button previously called navigateToSetup() (sending the user *to* the
setup view) and never marked setup complete or set a directory, so App.tsx
fell back to OnboardingFlow because of the !selectedDirectory guard. The
guard existed solely to paper over this broken state.

Wire the button to a dedicated handleSkip that completes onboarding +
setup and routes to task-input, drop the App.tsx guard, and show the
button in production as well as dev. TaskInput already handles an empty
selectedDirectory via mostRecentRepo.

Generated-By: PostHog Code
Task-Id: c5a0b893-61f1-40a5-8f84-8d93c1ad2dba
Generated-By: PostHog Code
Task-Id: c5a0b893-61f1-40a5-8f84-8d93c1ad2dba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants