Repository navigation
feat(setup): ask only what has no default in the first-run wizard - #376
Merged
Merged
Conversation
The setup wizard walked through every step (namespace, storage, model, budget, apps, telemetry) even when each had a default. It now asks only for a model provider, and a budget for a paid cloud model; the rest is one click away and in Settings. When the installer or .env already set the model, setup finishes at startup and the wizard doesn't open. GET /setup and lens_status say what's left (todo), so an agent knows too. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014Y4mUBxDN6pTR2fykqrfYV
Baselines from this PR's own Clicks run (artifact clicks). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014Y4mUBxDN6pTR2fykqrfYV
Merged
16 of 22 tasks
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
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.
Requested by Adeel · project thread
Description
Before: after the first sign-in, the setup wizard walked through every step (namespace, storage, model provider, budget, apps, telemetry), each already defaulted, even when the installer had set the model provider.
After: the wizard asks only for what has no answer: a model provider, and a budget when that model is a paid cloud one (a model on this machine or this network needs none). Namespace, storage, apps and telemetry are one click away under "With defaults, if you'd like to choose" and stay in Settings. When the installer or
.envalready set the model, setup finishes at startup and the wizard never opens.GET /api/v1/setupand thelens_statustool say what's left (todo), so an agent knows too.How:
setup.todo()decides from the effective settings (llmwithout base URL or model →llm; a cloud model with no overall budget that the installer didn't seed →budget);setup.finish_if_ready()runs inprepare(). The wizard builds its flow fromtodoonce. The clicks journey for the wizard is now one click ("Save and continue"); the Clicks baseline comes from this PR's CI artifact.Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly. (configuration.md First-run setup, get-started.md, storage.md, telemetry.md)## UnreleasedinCHANGELOG.md. (n/a)Done questions (AGENTS.md)
todoinGET /setupandlens_status.make openapi) updated.🤖 Generated with Claude Code
https://claude.ai/code/session_014Y4mUBxDN6pTR2fykqrfYV
Generated by Claude Code