Summary

The official iOS app (openclaw-ios) renders assistant markdown tables and headers as raw source text. A standard pipe table arrives as a wall of | characters and ### headers show literally, where the web Control UI renders the same message correctly.

Repro

1. From the iOS app, have the assistant reply with a standard markdown table, e.g.:

   | Model | Size | Speed |
   |---|---|---|
   | tiny | 75MB | ~10x |
   | large-v3 | 3GB | 1x |
   

2. Compare the same message in the web Control UI.

Expected

Either render the table natively, or degrade gracefully (bullets/code block) the way other channels do. Per docs/concepts/markdown-formatting.md, markdown.tables already supports code/bullets/off fallbacks for channels that can't render tables — the iOS/webchat surface appears not to apply any such conversion.

Actual

Raw markdown leaks through: table pipes and # heading markers are shown verbatim. Result is hard to read.

Environment

• Surface: iOS app (openclaw-ios), connecting via webchat surface
• Comparison surface: web Control UI (renders correctly)

Related

• [Bug]: iOS app: Assistant response line breaks not rendered #98028 (iOS app: assistant response line breaks not rendered) — same client, adjacent rendering gap. This issue covers rich markdown (tables/headers) specifically, not just newlines.