Model Configuration changes can be applied to .ENV or other file #47
Description
Is your feature request related to a problem? Please describe.
Currently, updating model configuration requires modifying the application code or redeploying services. This makes it cumbersome to adjust model parameters, switch models, or update API endpoints dynamically—especially in environments where configuration changes need to be applied quickly without code changes.
Describe the solution you'd like
I would like to have model configuration (e.g., model name, API keys, endpoints, or hyperparameters) managed through a .env file or a separate configuration file (like config.yaml or settings.json).
The application should automatically load or refresh configuration values from this file at startup (or even dynamically if possible).
This would allow developers or administrators to modify settings without redeploying the application.
Additional context
Example use case:
MODEL_NAME=gpt-5
MODEL_ENDPOINT=https://api.openai.com/v1
MODEL_TEMPERATURE=0.7