[GH-ISSUE #20622] feat: force Agentic (Native tool calling mode) Knowledge base retrieval #138965

New Issue

GiteaMirror · 2026-05-25T11:59:14-05:00

GiteaMirror commented

2026-05-25 11:59:14 -05:00

Originally created by @jegranado on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20622

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Hello,

The Agentic KB query is blazing fast comparing to the former way of hitting RAG content.
It works really well.... when it works 🫠

I have to constantly ask the model to try looking at the KB to find relevant information, but it is not consistent, and more often than not it reverts to the model's own data.

Desired Solution you'd like

I'd like to have the option to force the query_knowledge_* function calls for a given model.

It works so well - when it works.

Alternatives Considered

I've tried some Prompt Engineering, but it's not bulletproof.
Maybe my real answer is finetuning?

Additional Context

I do have a situation where I have "more detailed"/"preferred" information about things that are open to the world, so the LLMs tend to have outdated/misleading information about what my users are asking for.

Originally created by @jegranado on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20622 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Hello, The Agentic KB query is blazing fast comparing to the former way of hitting RAG content. It works really well.... when it works 🫠 I have to constantly ask the model to try looking at the KB to find relevant information, but it is not consistent, and more often than not it reverts to the model's own data. ### Desired Solution you'd like I'd like to have the option to force the query_knowledge_* function calls for a given model. It works *so well* - when it works. ### Alternatives Considered I've tried some Prompt Engineering, but it's not bulletproof. Maybe my real answer is finetuning? ### Additional Context I do have a situation where I have "more detailed"/"preferred" information about things that are open to the world, so the LLMs tend to have outdated/misleading information about what my users are asking for.

GiteaMirror closed this issue

2026-05-25 11:59:15 -05:00

GiteaMirror commented

2026-05-25 11:59:16 -05:00

@Classic298 commented on GitHub (Jan 12, 2026):

Model limitation, you can't force the model to use it, the model needs to choose to use the tool

you can only improve that via prompting and/or system prompt and telling the model to make use of it

@Classic298 commented on GitHub (Jan 12, 2026): Model limitation, you can't force the model to use it, the model needs to choose to use the tool you can only improve that via prompting and/or system prompt and telling the model to make use of it

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#138965