feat: configure provider defaults for new threads - #55
Merged
Conversation
- Add per-provider model traits and permission-mode defaults - Apply configured defaults across web and mobile new-thread flows
…rovider-defaults # Conflicts: # apps/web/src/components/settings/settingsSearch.test.ts
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
Why
Users can now define provider-specific defaults once and have new threads consistently start with the intended model, options, and runtime mode. Explicit selections continue to take precedence. The migration and cookie changes simplify fork maintenance and improve isolation for parallel development servers.
UI Changes
This changes the provider settings UI and new-thread model selection behavior. Before/after screenshots are not included.
Checklist