[Feature]: Allow to display messages as plain text

[ServeurpersoCom]

Browser

All

Description

User messages are now rendered as plain text instead of Markdown.
This prevents Markdown from breaking when users paste code or send content that looks like reasoning blocks.

Assistant messages keep their Markdown rendering, so formatting, links and lists still work as expected.

Changes

Added isAssistant check before rendering reasoning content.

User messages displayed with whitespace-pre-wrap instead of MarkdownDisplay.

Why
Without this change, sending code or -like content as a user could break formatting or leak into the reasoning renderer.

Proposal : main...ServeurpersoCom:llama.ui:assistant-markdown-only

Steps to Reproduce

Paste any Markdown into a user message.

Paste code containing # comments or long sequences of #######.

Observe that rendering breaks or overflows to the right.

Expected Behavior

UI should display any coding work safely as plain text.

No horizontal overflow when users paste code.

Assistant responses continue to render Markdown normally.

Version

No response

Additional Context

No response

[olegshulyakov]

@ServeurpersoCom Do you wrap Markdown with triple ` symbol, see Quoting code?

[ServeurpersoCom]

@ServeurpersoCom Do you wrap Markdown with triple ` symbol, see Quoting code?

I'm aware of Markdown quoting with triple backticks.
The problem here is not user misuse of Markdown syntax, but that any raw Markdown (e.g. #, ---, ####) inside a user message is currently parsed as Markdown by the UI renderer. This can leak into reasoning blocks or break layout (horizontal overflow).
My proposal explicitly disables Markdown rendering for user messages and switches to white-space: pre-wrap, while keeping assistant messages in Markdown. That way:
Code or pseudo-Markdown from the user is displayed safely as plain text.
Assistant responses keep rich Markdown formatting.
It's a design choice for robustness: fail-safe rendering vs depending on every user to always wrap with triple backticks.

For reference, the Svelte WebUI of llama.cpp has made the exact same design choice: plain text for user input, Markdown only for assistant output.
We could eventually make this behavior configurable (toggle Markdown on/off for user messages).
However, for coding use-cases it’s critical that Markdown rendering is disabled by default for user input. Otherwise, source code pasted by the user becomes unreadable or broken by unintended formatting.

[ServeurpersoCom]

I just realized the title I used for this issue was confusing / misleading, sorry about that.

[olegshulyakov]

The problem here is not user misuse of Markdown syntax, but that any raw Markdown (e.g. #, ---, ####) inside a user message is currently parsed as Markdown by the UI renderer. This can leak into reasoning blocks or break layout (horizontal overflow).

Hasn't #182 fixed that?

[ServeurpersoCom]

The problem here is not user misuse of Markdown syntax, but that any raw Markdown (e.g. #, ---, ####) inside a user message is currently parsed as Markdown by the UI renderer. This can leak into reasoning blocks or break layout (horizontal overflow).

Hasn't #182 fixed that?

That change fixes horizontal overflow inside existing Markdown code blocks, which is good.

But the issue I raised is different: when a user message contains raw Markdown (#, ---, #### etc.), it is still parsed as Markdown instead of being displayed literally. This can break formatting or leak into the reasoning renderer.

My proposal is about disabling Markdown rendering for user messages entirely (plain text with white-space: pre-wrap), while keeping Markdown for assistant messages. The CSS change alone doesn’t address that.

[ServeurpersoCom]

Old llama.cpp legacy WebUI (obsolete, no fix)

llama.ui WebUI (with this fix)

Svelte refactor stock from llama.cpp

OpenAI ChatGPT Website :)

[ServeurpersoCom]

The patch still works after the last refactor and remains useful for maintaining the ability to send source code to LLM

[olegshulyakov]

@ServeurpersoCom I do not like that those interfaces do not render markdown if user paste it. I will close this one since there is an ability to display Markdown in code quotes.