fix(assistant): render markdown in TextInput output

[n-iv]

Summary

The assistant's "generate text" form currently displays its output through NcRichContenteditable, which renders text as-is. When the underlying LLM returns markdown (heading, lists, tables, bold, links), the user sees raw markdown syntax instead of formatted content.

This PR wraps the output field in NcRichText when isOutput is true, falling back to NcRichContenteditable for the input case. Headings, lists, bold, italic, code blocks and links are now rendered. Tables are not rendered due to the markdown-it configuration of NcRichText in @nextcloud/vue, which does not enable the table plugin by default. The copy still functions and keeps the markdown as expected.

Screenshots

Before

After

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Renders markdown content in the assistant's "generate text" output by using NcRichText for output mode while keeping NcRichContenteditable for input mode.

Changes:

• Conditionally render NcRichText when isOutput && hasValue is true.
• Import and register the NcRichText component.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[janepie]

Thank you for this PR! The problem with this is that is makes the output uneditable for the user, and we assume that the LLM output is not perfect and has to be adapted. Can you find a way to keep that function, and also keep the "easy copy" button?

[n-iv]

Hi @janepie, the easy copy button is still present and can be used. I added a very short video to show it.
Screencast_20260518_101227.webm

[janepie]

Ah thanks for showing me! It's a bit unfortunate that the button and the AI-generation note disappear into the scrollable area, we should keep them visible and make the result scrollable instead.

So points to adapt would be

• keep an easy way to edit the result (for example change into edit mode with a doubleclick on the area)

• always keep copy button and AI note in sight and make the result scrollable instead

[n-iv]

I pushed a new commit addressing both points:

• Double-clicking the rendered output now switches it to an editable contenteditable, which returns to rendered mode on blur. A title attribute hints at the affordance.
• The rendered output (and the editable variant in output mode) is now wrapped in a bounded scrollable container, so the result scrolls inside the component instead of pushing the copy button and the AI-generation note out of sight.

[janepie]

Looks good!
I'd prefer to have the double-click hint somewhere more visible but I'm not sure yet where to put it, so let's do that in a follow-up.

A few small remarks

[julien-nc]

Nice change! I like the increase of the max-height.

To make this more discoverable, there could be an "edit" button in the top right corner when it's not editable. Wdyt @janepie and @n-iv ? It would require to slightly increase the min-height so this edit button does not overlap with the copy one.

I spotted a minor bug, when the field is empty, we can only type one character and it leaves the edit mode. A double click is necessary to continue editing. This does not happen when the field is not empty. I'd say it's fine if we don't find an easy fix for that.

[n-iv]

Remove the block and the copy button ends up bottom-left and outside the output box instead of overlaying it. I'd keep it unless you see a different intent behind.

[julien-nc]

Thanks for the adjustments.

For the style issue, I can't reproduce.

Are you sure you're not tweaking the CSS? Are you using the custom_css app?
The border-radius of the input field and of the task items in the left navigation sidebar is wrong on your side.

Or maybe your server-injected CSS is different. Which version of NC are you using?

[julien-nc]

Also, you need to sign your commits. Check the DCO check output.

[n-iv]

Rebased on main and squashed into a single commit. Dropped the z-index as suggested => no visible difference, as @julien-nc noticed. And to answer that last question, yes we use a lot of css on our instances. Ready for another look.

[julien-nc]

• Rebased on main
• Adjusted the min height of NcRichText (we changed that in other places recently)
• Made sure NcRichText is scrolling to bottom while its content is streamed (recent change as well)
• Force pushed

One remaining question: What is the change in TaskTypeSelect.vue about? If it's unrelated, let's remove it.
Once we sort this out we can get this in!