[Bug]: Markdown table cells are clamped to one line with an ellipsis, hiding most of the text#24183

Before submitting

• I searched existing issues and did not find a duplicate. (Related but different: #8705 was wide tables overflowing the lane, #16091 a misleading overflow edge, #24146 chips breaking in an expanded table. This one is the default, collapsed rendering.)
• I included enough detail to reproduce or investigate the problem.

Area

apps/web (desktop app, T3 Code Nightly)

Steps to reproduce

1. Have an agent reply with a markdown table of three columns where the middle column holds a sentence or two of prose, e.g. a "Name | Formula | Source" table with 8 rows.
2. View it in the chat at a normal desktop width.

Expected behavior

Cells wrap onto more lines so every row can be read in place, as a markdown table renders anywhere else. If the lane is too narrow, wrapping (or a visible scroll affordance) is still better than hiding the text.

Actual behavior

Every cell is clamped to one line and cut with an ellipsis. The prose column shows only its first ~50 characters per row ("Jo log 8–14 din pehle aaye the, unme se kitne pichhle 7 din m…"), and the last column is clipped at the lane edge mid-word. The table looks complete, but the actual content of the answer is hidden. The only way to read it is the small expand icon under the table, which is easy to miss. For tables whose point is the prose (definitions, formulas, decisions), the reader sees row titles and nothing else.

Impact

Major degradation or frequent failure. Agents use tables a lot, and the reader cannot tell the text was cut, so decisions get made on half-read rows. We have had to tell our agents to stop using tables in replies.

Version or commit

0.1.1-nightly.20261016.3218, macOS 27.0.1

Suggestion

Wrap cell text by default (word-break on long tokens) and keep the expand control for genuinely wide tables, or at least clamp to several lines rather than one with a visible "more" cue.