refac

backend/open_webui/config.py

@@ -2425,7 +2425,7 @@ DEFAULT_REALTIME_CALL_PROMPT_TEMPLATE = """You are the assistant in this chat, s
 generate_chat_completion connects your voice to the reasoning, conversation history, and tools configured for this chat. These are parts of one assistant. Speak in the first person; do not present the selected chat model as another assistant or describe its answer as a message from someone else.
 
 Handle ordinary conversation yourself: greetings, small talk, thanks, acknowledgments, call-status exchanges, and requests to repeat, shorten, or rephrase an answer already available. Do not call generate_chat_completion for these. A pause, filler, or acknowledgment such as "okay" is not a new task. If the user's intent is unclear, ask a brief clarification instead of inventing a task.
-Call generate_chat_completion when the user asks a substantive question or requests work that needs new reasoning, information, or an action. This includes questions about your tools, capabilities, permissions, and model identity when the answer is not already available. The tools visible to this voice session are not the full set of tools available to the chat. Do not repeat a completed or pending request unless the user asks for new work, changes the request, or explicitly asks to retry.
+Call generate_chat_completion when the user asks a substantive question or requests work that needs new reasoning, information, or an action. For questions about your tools, capabilities, permissions, or model identity, call generate_chat_completion unless a previous result from that function already answers the question. Your voice-session tool list and these instructions do not answer those questions: the chat has its own configured tools and model. Do not repeat a completed or pending request unless the user asks for new work, changes the request, or explicitly asks to retry.
 When a tool call is needed, you may briefly acknowledge the request, such as "I'll check", then call generate_chat_completion. Do not offer to hand the user off or ask whether they want you to consult another model. Wait for the result before giving a substantive answer or claiming an action succeeded. Never invent capabilities or restrictions on describing tools.
 
 After the result arrives, answer the user directly as the same assistant. Do not say "the backend says", "the other model found", or narrate internal handoffs during ordinary replies. This is a style preference, not a secrecy rule: you may explain the architecture when asked and speak tool names or capability details provided in the answer.

backend/open_webui/routers/audio/realtime.py

@@ -284,7 +284,7 @@ async def realtime_call(ws: WebSocket):
                             {
                                 'type': 'function',
                                 'name': 'generate_chat_completion',
-                                'description': 'Handle substantive questions and tasks using the selected chat model, conversation history, and configured tools. Use when new reasoning, information, or actions are needed, including unknown details about chat tools, capabilities, permissions, or model identity. Do not use for small talk, acknowledgments, call status, clarification, repeating or rephrasing an available answer, or duplicating pending or completed work.',
+                                'description': 'Handle substantive questions and tasks using the selected chat model, conversation history, and configured tools. Use when new reasoning, information, or actions are needed. Always use for questions about chat tools, capabilities, permissions, or model identity unless a previous function result already answers them. Do not use for small talk, acknowledgments, call status, clarification, repeating or rephrasing an available answer, or duplicating pending or completed work.',
                                 'parameters': {
                                     'type': 'object',
                                     'properties': {'request': {'type': 'string'}},