refactor: move model configurations to JSON and improve model management #451
Conversation
This file contains 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
- Move models data from models.ts to models.json - Update model type definition - Add models prop to Chat and ModelSelector components - Update pages to pass models from json
- Change cookie key from 'modelId' to 'selectedModel' - Store entire model object as JSON string in cookie - Add error handling for JSON parsing - Update model selection handling
- Update model cookie handling to use new JSON format - Add error handling for JSON parsing - Update DEFAULT_MODEL to use simple model ID - Maintain default provider as 'openai' - Improve error response format
- Add o3-mini model - Reorder models - Update model configurations with proper toolCallType and toolCallModel - Move OpenAI Compatible model to the end
- Remove model-specific environment variables from .env.local.example - Add JSON-based model configuration documentation to CONFIGURATION.md - Update AI providers section in README.md
- Update route.ts to use Model object directly - Update streaming functions to handle Model object - Update context window calculation to use Model object - Improve message truncation logic
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Model Management Refactoring
This PR addresses issue #422 by refactoring the model management system to use a JSON-based configuration approach and improving the handling of model objects throughout the application.
Changes
Model Configuration
lib/config/models.jsonenabled: to control model availabilitytoolCallType: to specify if model supports native tool calls or requires manual handlingtoolCallModel: to specify which model to use for tool calls (whentoolCallTypeis "manual")Example configuration:
{ "id": "model-id", "name": "Model Name", "provider": "Provider Name", "providerId": "provider-id", "enabled": true, "toolCallType": "native|manual", "toolCallModel": "tool-call-model-id" }