Long URLs wrap incorrectly in Ask mode chat replies

[AmyShang-alt]

Problem

In project-level Ask mode, long URLs in assistant replies wrap incorrectly in the left chat pane. The text can be split in the middle of a word or hostname.

Example from the screenshot:

• https://github.com/nexu-io/open-design is split as https://githu plus b.com/nexu-io/open-design on the next line.
• The official site link, https://open-design.ai/, is also squeezed into the same paragraph, making the response harder to read.

Steps to Reproduce

1. Open any project.
2. Switch the chat composer to Ask mode.
3. Ask something like open design 是什么.
4. Check the left chat pane when the assistant response includes long links such as GitHub or official website URLs.

Actual Result

Long URLs are broken awkwardly within the narrow chat pane, including in the middle of domains or words. Visually, the link looks broken.

Expected Result

Long links should render in a more readable way, for example:

• Wrap as complete clickable links without splitting the hostname into hard-to-read fragments.
• Or render as Markdown/shortened display links while preserving the full target URL.
• At minimum, the narrow chat pane should not show unnatural splits such as githu / b.com.

Impact

This affects readability and link trust in Ask mode answers, especially for common responses that include project introductions, documentation links, official websites, or GitHub URLs.

Environment

• Open Design local Electron
• PR runtime: pr4862
• Page: project chat + Design Files split view

[lefarcen]

Hey @AmyShang-alt — thanks for the clear repro. The githu / b.com split is consistent with the current bare-URL rendering path in the chat panel: the markdown renderer autolinks raw https://... text with the md-link-bare class in apps/web/src/runtime/markdown.tsx, and that class currently applies word-break: break-all in apps/web/src/styles/viewer/code.css, which would force hostname breaks in a narrow sidebar.

I’ve labeled this as a bug. The most likely fix is to soften the wrap behavior for bare links in the assistant message path — e.g. keep the link clickable but remove break-all in favor of a less aggressive wrap rule, or render a shortened display label while preserving the full href underneath.

[lefarcen]

Heads-up: PR #4919 is up for this. It targets the bare-link wrap rules in apps/web/src/styles/viewer/code.css, replacing the aggressive break-all / anywhere combo with URL-specific wrapping and adding a focused regression test so raw GitHub-style links stay readable in the Ask sidebar.

Keeping this issue open until that fix lands.