I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.8.12
Ollama Version (if applicable)
No response
Operating System
Arch Linux
Browser (if applicable)
Firefox 148.0.2
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
When generating a response including tool calls, with "always expand details" turned on, the details should not automatically collapse after the second tool call.
Actual Behavior
When the second tool call happens, the details collapse into "Explored X, Y...". Manual action is needed to expand them again.
Steps to Reproduce
Start with a clean Open WebUI install
Set up a model with native tool calling functions
Enable "Always Expand Details" in the user settings
Ask for a question that requires multiple-step tool calling, like asking it to search and fetch data
Originally created by @limdingwen on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23255
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.8.12
### Ollama Version (if applicable)
_No response_
### Operating System
Arch Linux
### Browser (if applicable)
Firefox 148.0.2
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
When generating a response including tool calls, with "always expand details" turned on, the details should not automatically collapse after the second tool call.
### Actual Behavior
When the second tool call happens, the details collapse into "Explored X, Y...". Manual action is needed to expand them again.
### Steps to Reproduce
1. Start with a clean Open WebUI install
2. Set up a model with native tool calling functions
3. Enable "Always Expand Details" in the user settings
4. Ask for a question that requires multiple-step tool calling, like asking it to search and fetch data
### Logs & Screenshots
<img width="1111" height="47" alt="Image" src="https://github.com/user-attachments/assets/d7af2553-1170-47a2-8815-d333bdc6f7a8" />
<img width="459" height="75" alt="Image" src="https://github.com/user-attachments/assets/8640463b-7f46-4153-8f46-5de7b571a088" />
### Additional Information
This is directly related to #21604 and https://github.com/open-webui/open-webui/commit/261aec8c864646eb7215be0d5c14a79cad3cb93f as introduced in https://github.com/open-webui/open-webui/releases/tag/v0.8.11.
GiteaMirror
added the bug label 2026-05-15 15:57:28 -05:00
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 @limdingwen on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23255
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.8.12
Ollama Version (if applicable)
No response
Operating System
Arch Linux
Browser (if applicable)
Firefox 148.0.2
Confirmation
README.md.Expected Behavior
When generating a response including tool calls, with "always expand details" turned on, the details should not automatically collapse after the second tool call.
Actual Behavior
When the second tool call happens, the details collapse into "Explored X, Y...". Manual action is needed to expand them again.
Steps to Reproduce
Logs & Screenshots
Additional Information
This is directly related to #21604 and https://github.com/open-webui/open-webui/commit/261aec8c864646eb7215be0d5c14a79cad3cb93f as introduced in https://github.com/open-webui/open-webui/releases/tag/v0.8.11.
@tjbck commented on GitHub (Apr 1, 2026):
Addressed in dev.