Use the TTS button beneath a chat.
Click the action function that updates user voice settings via the OWUI API. (https://github.com/FooleanBool/openwebui/tree/main/functions/actions/quick-voice-conf)
Click the TTS button and listen to the generated speech with the previous settings.
Change active chat and go back, click TTS button, new settings are applied.
Steps to Reproduce
Use the TTS button under chat.
Update voice settings (for user, not global) using API or action button mentioned.
Click TTS and listen.
Change to a new chat/menu.
Return to original chat.
Hear new settings applied.
Logs & Screenshots
There are no logs to show as all operations are successful.
Additional Information
I have the same action button setup for quick image config, these settings are applied immediately on API update.
Originally created by @FooleanBool on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12193
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.5.20 / v0.6.0
### Ollama Version (if applicable)
v0.6.3
### Operating System
Ubuntu 24.04
### Browser (if applicable)
Brave v1.76.82 / Vanadium 135.0.7049.38
### 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 listed steps to reproduce the bug in detail.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
### Expected Behavior
Use the TTS button beneath a chat.
Click the action function that updates user voice settings via the OWUI API. (https://github.com/FooleanBool/openwebui/tree/main/functions/actions/quick-voice-conf)
Click the TTS button and listen to the generated speech according to the updated config.
### Actual Behavior
Use the TTS button beneath a chat.
Click the action function that updates user voice settings via the OWUI API. (https://github.com/FooleanBool/openwebui/tree/main/functions/actions/quick-voice-conf)
Click the TTS button and listen to the generated speech with the previous settings.
Change active chat and go back, click TTS button, new settings are applied.
### Steps to Reproduce
1. Use the TTS button under chat.
2. Update voice settings (for user, not global) using API or action button mentioned.
3. Click TTS and listen.
4. Change to a new chat/menu.
5. Return to original chat.
6. Hear new settings applied.
### Logs & Screenshots
There are no logs to show as all operations are successful.
### Additional Information
I have the same action button setup for quick image config, these settings are applied immediately on API update.
GiteaMirror
added the bug label 2026-04-19 22:24: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 @FooleanBool on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12193
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.5.20 / v0.6.0
Ollama Version (if applicable)
v0.6.3
Operating System
Ubuntu 24.04
Browser (if applicable)
Brave v1.76.82 / Vanadium 135.0.7049.38
Confirmation
README.md.Expected Behavior
Use the TTS button beneath a chat.
Click the action function that updates user voice settings via the OWUI API. (https://github.com/FooleanBool/openwebui/tree/main/functions/actions/quick-voice-conf)
Click the TTS button and listen to the generated speech according to the updated config.
Actual Behavior
Use the TTS button beneath a chat.
Click the action function that updates user voice settings via the OWUI API. (https://github.com/FooleanBool/openwebui/tree/main/functions/actions/quick-voice-conf)
Click the TTS button and listen to the generated speech with the previous settings.
Change active chat and go back, click TTS button, new settings are applied.
Steps to Reproduce
Logs & Screenshots
There are no logs to show as all operations are successful.
Additional Information
I have the same action button setup for quick image config, these settings are applied immediately on API update.