I have searched the existing issues and discussions.
Problem Description
Currently, function calling will transfer tools to either model itself, which needs APIs or models support native function calling, or external model, which can hardly achieve an expected result.
Desired Solution you'd like
Can we add one "compatibility" option in model settings, making all function calling work just like the code interpreter? That is, transfer prompt about "Tools available" directly to models.
If so, for some APIs or models that do not support native function calling, they can smoothly work with tools. It will definitely better than relying on external model for most cases.
Alternatives Considered
No response
Additional Context
No response
Originally created by @funnycups on GitHub (May 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13842
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Currently, function calling will transfer tools to either model itself, which needs APIs or models support native function calling, or external model, which can hardly achieve an expected result.
### Desired Solution you'd like
Can we add one "compatibility" option in model settings, making all function calling work just like the code interpreter? That is, transfer prompt about "Tools available" directly to models.
If so, for some APIs or models that do not support native function calling, they can smoothly work with tools. It will definitely better than relying on external model for most cases.
### 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 @funnycups on GitHub (May 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13842
Check Existing Issues
Problem Description
Currently, function calling will transfer tools to either model itself, which needs APIs or models support native function calling, or external model, which can hardly achieve an expected result.
Desired Solution you'd like
Can we add one "compatibility" option in model settings, making all function calling work just like the code interpreter? That is, transfer prompt about "Tools available" directly to models.
If so, for some APIs or models that do not support native function calling, they can smoothly work with tools. It will definitely better than relying on external model for most cases.
Alternatives Considered
No response
Additional Context
No response