Originally created by @solesensei on GitHub (Mar 28, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
It seems that there is no way to pass custom parameters to the /chat/completions endpoint from the user interface.
Desired Solution you'd like
I want to set the extra parameters for my OpenAI-compatible server.
These parameters could be either parameters that are not currently supported in the UI or custom values that I want to use for tracing requests.
Extra model parameters:
{"mirostat":1,"some_key":"value"}
Alternatives Considered
No response
Additional Context
No response
Originally created by @solesensei on GitHub (Mar 28, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
It seems that there is no way to pass custom parameters to the `/chat/completions` endpoint from the user interface.
### Desired Solution you'd like
I want to set the **extra** parameters for my OpenAI-compatible server.
These parameters could be either parameters that are not currently supported in the UI or custom values that I want to use for tracing requests.
**Extra model parameters:**
```json
{ "mirostat": 1, "some_key": "value" }
```
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @solesensei on GitHub (Mar 28, 2025).
Check Existing Issues
Problem Description
It seems that there is no way to pass custom parameters to the
/chat/completionsendpoint from the user interface.Desired Solution you'd like
I want to set the extra parameters for my OpenAI-compatible server.
These parameters could be either parameters that are not currently supported in the UI or custom values that I want to use for tracing requests.
Extra model parameters:
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Mar 28, 2025):
As mentioned in countless previous discussions and issues, you should use Functions for this.