feat: redesign onboarding — auto-detect runtimes, remove install step#547
Merged
feat: redesign onboarding — auto-detect runtimes, remove install step#547
Conversation
Replace the 4-card runtime installation step with auto-detection in the Welcome screen. Runtimes are now detected and displayed as a status list (installed/authenticated/not installed) without requiring users to install anything during onboarding. Runtime management moves exclusively to Settings > Agent Runtimes. Changes: - Remove agent-runtimes from onboarding wizard steps (4→3 local, 5→4 gateway) - Redesign StepWelcome with runtime status list + live system status chips - Delete step-agent-runtimes.tsx (592 lines) — Settings handles this now - Consolidate step definitions: API route imports from onboarding-flow.ts - Enhance empty-state-launchpad with version/auth details per runtime - Add i18n keys for runtime status labels (10 locales) - Fix runtime detection: search ~/.local/bin, ~/Library/pnpm, hermes --help - Fix Codex auth detection via OPENAI_API_KEY env var - Fix version string cleanup for LACP-wrapped binaries No migration needed — existing completed_steps arrays silently drop the removed step ID via parseCompletedSteps validation.
github-actions
bot
added
the
screenshot-drift
📸 Screenshot Drift CheckThis PR modifies UI source files. Please verify whether the README screenshots need refreshing:
Changed UI filesSee This comment is posted automatically and can be dismissed if no visual changes occurred. |
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
Redesigns the onboarding wizard based on research into how other agent orchestration tools handle setup (Dify, CrewAI, AutoGen, Paperclip, LangSmith, etc.). The dominant pattern is "auto-detect and go" — not "install 4 runtimes from a wizard."
Before: 4-5 step wizard with a full runtime installation step (592-line component with inline Hermes config, OAuth device code flow, 2x2 grid of install cards)
After: 3-4 step wizard that auto-detects installed runtimes and shows status. Runtime management moves exclusively to Settings.
What changed
onboarding-flow.ts(was duplicated)~/.local/bin,~/Library/pnpm; hermes uses--helpprobe; codex checksOPENAI_API_KEYNet diff: +304/-712 (408 lines removed)
No migration needed —
parseCompletedStepssilently drops the removed step ID.Test plan
pnpm typecheck— passes (pre-existing errors only)pnpm test— 892/892 pass, 74/74 files