Is your feature request related to a problem? Please describe. Currently, the application only supports customizing the OpenAI URL and API key. This is great for users of OpenAI or services with identical API structures. However, many other AI providers now offer OpenAI-compatible APIs but may require different model names or have unique parameters. The current implementation makes it difficult to use these alternative AI providers. Describe the solution you'd like To greatly enhance the flexibility of the application, I propose the following additions: Custom Model Name: An input field to specify the model name (e.g., llama3-8b-8192, claude-3-opus-20240229,deepseek-chat). This is the most crucial change, as it would immediately enable compatibility with a wide range of AI providers that use custom model identifiers. (Optional but Recommended) Advanced Customization with Keywords: It would be even more powerful to allow users to customize the prompt and model temperature using keywords. For example:{{language}}: This keyword could be used in a custom prompt template to dynamically insert the target language. A dedicated field to set the temperature parameter for the API call. Describe alternatives you've considered A possible alternative is to create a complex proxy server to intercept and modify the requests before they are sent to the AI provider. However, this is a cumbersome and technically demanding solution for the end-user. Integrating these simple customization options directly into the application would be a much more user-friendly and efficient approach. Additional context Many AI providers, such as Groq, Together.ai , and various open-source models hosted on platforms like Replicate, now offer OpenAI-compatible APIs. Supporting custom model names would unlock access to these powerful and often more cost-effective solutions for all users. This would make the application a more versatile and valuable tool for a broader audience.