Add first-run configuration screen - #55
Merged
Merged
Conversation
Adds a first-run configuration screen to choose AI model provider.
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.
What changed
flow::without_modelto handle steps when no model is configured.llmservice to include a newProviderKind::Offfor no model configuration.FirstRunfor the first-run configuration.Why
The first-run configuration screen is necessary to ask the user what, if anything, writes the commit messages. This is a critical choice that affects the entire workflow of the application. The screen preselects based on the detected environment and allows the user to choose between running a local model, using a hosted API, or running without AI. This ensures a smooth onboarding experience and prevents the user from getting stuck in a configuration that doesn't work for them.
How to test