Originally created by @sings-to-bees-on-wednesdays on GitHub (Aug 14, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
Hi,
In our internal deployment of Open WebUI, we have received feedback that users are frustrated by the "Rich Text Input" feature. The problem arises when they try to paste text with special characters (e.g. program source code), which are then converted to rich formatting.
The "Rich Text Input" feature converts pasted characters from Markdown formatting to formatted text, and when the prompt is submitted, the formatted text is converted back to Markdown. However, this process is lossy, and can corrupt the user input. For example, _test_var = _foo_bar * _bar_foo * _foo_foo * _bar_bar is corrupted into _test_var = _foo_bar _barfoo_ _foo_foo * _bar_bar.
Desired Solution you'd like
I think we should mirror what chatgpt.com does, and not attempt to interpret user input as using any particular formatting syntax (Markdown or otherwise). As such, user-entered text should be always treated as plain text.
In practice, I think "Rich Text Input" should either be disabled by default, or there be a global (site-wide) setting which disables it.
Alternatives Considered
Some alternative ways to approach this could be:
Have the Rich Text Input feature somehow detect when the user is pasting code.
Have the Rich Text Input perfectly preserve formatting characters, so that even if they're interpreted as Markdown, the model can see the exact pasted string when the message is submitted.
Make it easier and straight-forward to paste code as a code block (e.g. typing ``` is not discoverable for people not versed in Markdown or not expecting typed text to be formatted as Markdown).
Additional Context
No response
Originally created by @sings-to-bees-on-wednesdays on GitHub (Aug 14, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Hi,
In our internal deployment of Open WebUI, we have received feedback that users are frustrated by the "Rich Text Input" feature. The problem arises when they try to paste text with special characters (e.g. program source code), which are then converted to rich formatting.
The "Rich Text Input" feature converts pasted characters from Markdown formatting to formatted text, and when the prompt is submitted, the formatted text is converted back to Markdown. However, this process is lossy, and can corrupt the user input. For example, `_test_var = _foo_bar * _bar_foo * _foo_foo * _bar_bar` is corrupted into `_test_var = _foo_bar _barfoo_ _foo_foo * _bar_bar`.
### Desired Solution you'd like
I think we should mirror what chatgpt.com does, and not attempt to interpret user input as using any particular formatting syntax (Markdown or otherwise). As such, user-entered text should be always treated as plain text.
In practice, I think "Rich Text Input" should either be disabled by default, or there be a global (site-wide) setting which disables it.
### Alternatives Considered
Some alternative ways to approach this could be:
- Have the Rich Text Input feature somehow detect when the user is pasting code.
- Have the Rich Text Input perfectly preserve formatting characters, so that even if they're interpreted as Markdown, the model can see the exact pasted string when the message is submitted.
- Make it easier and straight-forward to paste code as a code block (e.g. typing ```` ``` ```` is not discoverable for people not versed in Markdown or not expecting typed text to be formatted as Markdown).
### Additional Context
_No response_
@sings-to-bees-on-wednesdays commented on GitHub (Aug 14, 2025):
You can disable it from interface settings.
Thank you, how to do this for all users (globally), please?
@sings-to-bees-on-wednesdays commented on GitHub (Aug 14, 2025):
> You can disable it from interface settings.
Thank you, how to do this for all users (globally), please?
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 @sings-to-bees-on-wednesdays on GitHub (Aug 14, 2025).
Check Existing Issues
Problem Description
Hi,
In our internal deployment of Open WebUI, we have received feedback that users are frustrated by the "Rich Text Input" feature. The problem arises when they try to paste text with special characters (e.g. program source code), which are then converted to rich formatting.
The "Rich Text Input" feature converts pasted characters from Markdown formatting to formatted text, and when the prompt is submitted, the formatted text is converted back to Markdown. However, this process is lossy, and can corrupt the user input. For example,
_test_var = _foo_bar * _bar_foo * _foo_foo * _bar_baris corrupted into_test_var = _foo_bar _barfoo_ _foo_foo * _bar_bar.Desired Solution you'd like
I think we should mirror what chatgpt.com does, and not attempt to interpret user input as using any particular formatting syntax (Markdown or otherwise). As such, user-entered text should be always treated as plain text.
In practice, I think "Rich Text Input" should either be disabled by default, or there be a global (site-wide) setting which disables it.
Alternatives Considered
Some alternative ways to approach this could be:
```is not discoverable for people not versed in Markdown or not expecting typed text to be formatted as Markdown).Additional Context
No response
@tjbck commented on GitHub (Aug 14, 2025):
You can disable it from interface settings.
@sings-to-bees-on-wednesdays commented on GitHub (Aug 14, 2025):
Thank you, how to do this for all users (globally), please?
@m3ngyang commented on GitHub (Sep 21, 2025):
hi, how to disable it? @tjbck
@rgaricano commented on GitHub (Sep 21, 2025):
User Settings/Interface/Input section