You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Streaming replies re-parse only their last markdown block #1753
src/components/Markdown.tsx re-parses the whole reply on every throttled update, so long replies get slower to render and the newest text lags. Split streamed text at top-level block boundaries and memoize each finished block, so only the last block re-parses. Fall back to whole-text rendering for syntax that links blocks together (reference links, footnotes, open code fences).
Already on main: since #1475, MarkdownBody splits a streaming reply with markdownChunks and only the last (live) chunk re-parses. Settled chunks are memoized and cached (src/components/Markdown.tsx). Nothing to build. This was filed from a check against a stale checkout.
Activity
currentbits commentedon Oct 30, 2026
Already on main: since #1475, MarkdownBody splits a streaming reply with markdownChunks and only the last (live) chunk re-parses. Settled chunks are memoized and cached (src/components/Markdown.tsx). Nothing to build. This was filed from a check against a stale checkout.