Originally created by @nonlinear on GitHub (Jul 4, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
Currently, the only way to trigger a voice conversation in OpenWebUI is by clicking on button. It's fine but somewhat limited, since is the only method of triggering voice interaction. There needs to be additional, more flexible ways to trigger voice mode for improved accessibility.
Desired Solution you'd like
Voice Mode directly through a URL tag. By appending a specific tag to the URL, let's say, call=true or something, the conversation would automatically start in a call, so users can create their own "speed dial" solutions, bypassing point-and-click interface.
Alternatives Considered
Other methods such as adding keyboard shortcuts or voice commands were considered, but implementing the URL trigger is a more universal solution that simplifies access, especially for users who may rely on assistive technologies. It's simple for core developers, and it's empowering for users.
Additional Context
The addition of this feature would make OpenWebUI more accessible, allowing users to customize how they trigger voice mode. It supports diverse accessibility needs, ensuring a more inclusive experience for all users, particularly those who want to interact with system in different ways.
Originally created by @nonlinear on GitHub (Jul 4, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Currently, the only way to trigger a voice conversation in OpenWebUI is by clicking on button. It's fine but somewhat limited, since is the only method of triggering voice interaction. There needs to be additional, more flexible ways to trigger voice mode for improved accessibility.
### Desired Solution you'd like
Voice Mode directly through a URL tag. By appending a specific tag to the URL, let's say, `call=true` or something, the conversation would automatically start in a call, so users can create their own "speed dial" solutions, bypassing point-and-click interface.
### Alternatives Considered
Other methods such as adding keyboard shortcuts or voice commands were considered, but implementing the URL trigger is a more universal solution that simplifies access, especially for users who may rely on assistive technologies. It's simple for core developers, and it's empowering for users.
### Additional Context
The addition of this feature would make OpenWebUI more accessible, allowing users to customize how they trigger voice mode. It supports diverse accessibility needs, ensuring a more inclusive experience for all users, particularly those who want to interact with system in different ways.
@tjbck commented on GitHub (Jul 4, 2025):
This has existed for a very long time 😅
https://docs.openwebui.com/tutorials/integrations/firefox-sidebar#call-overlay
@tjbck oooo so if I append ?temporary-chat=true to say, a conversation URL, it automatically opens as call? Is it native to openwebUI? or just on firefox browsers? I'm confused.
(my server is down this week, so I can't test it myself, sorry)
@nonlinear commented on GitHub (Jul 4, 2025):
@tjbck oooo so if I append `?temporary-chat=true` to say, a conversation URL, it automatically opens as call? Is it native to openwebUI? or just on firefox browsers? I'm confused.
(my server is down this week, so I can't test it myself, sorry)
@tjbck oooo so if I append ?temporary-chat=true to say, a conversation URL, it automatically opens as call? Is it native to openwebUI? or just on firefox browsers? I'm confused.
(my server is down this week, so I can't test it myself, sorry)
Yes, you can append ?temporary-chat=true&call=true to the url and it will run temporary and start a call.
Here is an example but it will require https for microphone to work.
@Zyfax commented on GitHub (Jul 4, 2025):
> [@tjbck](https://github.com/tjbck) oooo so if I append `?temporary-chat=true` to say, a conversation URL, it automatically opens as call? Is it native to openwebUI? or just on firefox browsers? I'm confused.
>
> (my server is down this week, so I can't test it myself, sorry)
Yes, you can append `?temporary-chat=true&call=true` to the url and it will run temporary and start a call.
Here is an example but it will require https for microphone to work.
https://github.com/user-attachments/assets/1a4c6c17-bc6a-4390-80e0-0ccbf16e3379
It is not for Firefox only but that docs page is about Firefox Sidebar(could just be the wrong link but same url-params). The url-params is also described here (https://docs.openwebui.com/features/chat-features/url-params)
How come it’s not there when you click? Sometimes Openwebui feature are hidden in docs i don’t know.
I’ll be sending more feature suggestions and you folks let me know if maybe it’s already there, or it’s new.
@nonlinear commented on GitHub (Jul 5, 2025):
Ooo
Of course, we need https. nginx etc.
How come it’s not there when you click? Sometimes Openwebui feature are hidden in docs i don’t know.
I’ll be sending more feature suggestions and you folks let me know if maybe it’s already there, or it’s new.
I see. That was my confusion. It’s documented on a Firefox page, so I assumed it was Firefox-only. It’s global.
If I look at this documentation, is all of it global features too?
@nonlinear commented on GitHub (Jul 5, 2025):
I see. That was my confusion. It’s documented on a Firefox page, so I assumed it was Firefox-only. It’s global.
If I look at this documentation, is all of it global features too?
hm, I finally got my server back... turns out ?temporary-chat=true or ?voice=true doesn't work on safari which is the engine of all iOS browsers. Or does it? am I doing something wrong?
I wouldn't say a solution that only works in certain browsers a solution at all.
@nonlinear commented on GitHub (Aug 9, 2025):
hm, I finally got my server back... turns out ?temporary-chat=true or ?voice=true doesn't work on safari which is the engine of all iOS browsers. Or does it? am I doing something wrong?
I wouldn't say a solution that only works in certain browsers a solution at all.
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 @nonlinear on GitHub (Jul 4, 2025).
Check Existing Issues
Problem Description
Currently, the only way to trigger a voice conversation in OpenWebUI is by clicking on button. It's fine but somewhat limited, since is the only method of triggering voice interaction. There needs to be additional, more flexible ways to trigger voice mode for improved accessibility.
Desired Solution you'd like
Voice Mode directly through a URL tag. By appending a specific tag to the URL, let's say,
call=trueor something, the conversation would automatically start in a call, so users can create their own "speed dial" solutions, bypassing point-and-click interface.Alternatives Considered
Other methods such as adding keyboard shortcuts or voice commands were considered, but implementing the URL trigger is a more universal solution that simplifies access, especially for users who may rely on assistive technologies. It's simple for core developers, and it's empowering for users.
Additional Context
The addition of this feature would make OpenWebUI more accessible, allowing users to customize how they trigger voice mode. It supports diverse accessibility needs, ensuring a more inclusive experience for all users, particularly those who want to interact with system in different ways.
@tjbck commented on GitHub (Jul 4, 2025):
This has existed for a very long time 😅
https://docs.openwebui.com/tutorials/integrations/firefox-sidebar#call-overlay
@nonlinear commented on GitHub (Jul 4, 2025):
@tjbck oooo so if I append
?temporary-chat=trueto say, a conversation URL, it automatically opens as call? Is it native to openwebUI? or just on firefox browsers? I'm confused.(my server is down this week, so I can't test it myself, sorry)
@rgaricano commented on GitHub (Jul 4, 2025):
/?call=true

&
native
(chromium:)
@Zyfax commented on GitHub (Jul 4, 2025):
Yes, you can append
?temporary-chat=true&call=trueto the url and it will run temporary and start a call.Here is an example but it will require https for microphone to work.
https://github.com/user-attachments/assets/1a4c6c17-bc6a-4390-80e0-0ccbf16e3379
It is not for Firefox only but that docs page is about Firefox Sidebar(could just be the wrong link but same url-params). The url-params is also described here (https://docs.openwebui.com/features/chat-features/url-params)
@nonlinear commented on GitHub (Jul 5, 2025):
Ooo
Of course, we need https. nginx etc.
How come it’s not there when you click? Sometimes Openwebui feature are hidden in docs i don’t know.
I’ll be sending more feature suggestions and you folks let me know if maybe it’s already there, or it’s new.
@nonlinear commented on GitHub (Jul 5, 2025):
I see. That was my confusion. It’s documented on a Firefox page, so I assumed it was Firefox-only. It’s global.
If I look at this documentation, is all of it global features too?
@nonlinear commented on GitHub (Aug 9, 2025):
hm, I finally got my server back... turns out ?temporary-chat=true or ?voice=true doesn't work on safari which is the engine of all iOS browsers. Or does it? am I doing something wrong?
I wouldn't say a solution that only works in certain browsers a solution at all.