mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 14:39:31 -05:00
[GH-ISSUE #15173] issue: Custom Generation parameters for RAG does not work (OPENAI) #33019
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Mcthomas777 on GitHub (Jun 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15173
Originally assigned to: @jackthgu on GitHub.
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.13
Ollama Version (if applicable)
No response
Operating System
Ubuntu22.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Custom Generation parameters are pursue to custom llm service (compatible with openai) when using rag (generation over documents or knowledge base).
Actual Behavior
Custom parameters are not sent when loading documents beside, but parameters are sent when not using RAG.
I provided my raw HTTP body that Irecieved from openwebui (even so I customized max_tokens, I didnt received it in the request)
Steps to Reproduce
Logs & Screenshots
b'{"model":"gpt-4","messages":[{"role":"user","content":"### Task:\nAnalyze the chat history to determine the necessity of generating search queries, in the given language. By default, prioritize generating 1-3 broad and relevant search queries unless it is absolutely certain that no additional information is required. The aim is to retrieve comprehensive, updated, and valuable information even with minimal uncertainty. If no search is unequivocally needed, return an empty list.\n\n### Guidelines:\n- Respond EXCLUSIVELY with a JSON object. Any form of extra commentary, explanation, or additional text is strictly prohibited.\n- When generating search queries, respond in the format: { \"queries\": [\"query1\", \"query2\"] }, ensuring each query is distinct, concise, and relevant to the topic.\n- If and only if it is entirely certain that no useful results can be retrieved by a search, return: { \"queries\": [] }.\n- Err on the side of suggesting search queries if there is any chance they might provide useful or updated information.\n- Be concise and focused on composing high-quality search queries, avoiding unnecessary elaboration, commentary, or assumptions.\n- Today's date is: 2025-06-19.\n- Always prioritize providing actionable and broad queries that maximize informational coverage.\n\n### Output:\nStrictly return in JSON format: \n{\n \"queries\": [\"query1\", \"query2\"]\n}\n\n### Chat History:\n<chat_history>\nUSER: Wie plane ich ein Projekt?\n</chat_history>\n"}],"stream":false}'
Additional Information
No response
@tjbck commented on GitHub (Jun 21, 2025):
Instruction here isn't very clear, could you provide a thorough step by step guide? Screenshots/recording would be extremely helpful here.
@jackthgu commented on GitHub (Jun 23, 2025):
Hello,
To help us resolve this issue, we kindly ask you to provide the following information:
A screenshot of the current model configuration that includes the knowledge base — specifically showing whether max_token is set correctly.
The server logs at the moment the prompt is submitted (i.e., when the Enter key is pressed in the chat window). Please ensure the log level is set to DEBUG.
Please make sure this test is conducted in a new chat session.
Thank you in advance!