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
Render Markdown in REPL Sidekick conversations and round output #1342
Sidekick messages and the Output view for an executed REPL round can contain Markdown. Both should display its formatting in the terminal so headings, lists, links, and code are readable in place.
Acceptance
Render the same Markdown consistently in Sidekick conversation bodies and the visible Output of a REPL round. Cover headings, paragraphs, emphasis, lists, links, inline code, and fenced code. Keep fenced content literal, with its indentation and line breaks.
Fit formatted content to the available pane width. Keep incomplete Markdown readable as a reply streams and render it consistently when the reply settles or the session reopens.
Use descriptive link text and preserve the link target for inspection. Preserve the original text in stored messages, execution output, and raw inspection or copy paths.
Exercise a representative response on both surfaces in the real REPL at wide and narrow sizes. Include a plain-text case, a code fence, and a streamed or reopened message. Publish the usual visual evidence and paired typing timings.
Related to #931 and #1340. The CLI already uses the Markdown lexer for inline TODO formatting in packages/cli/src/repl/todo/inline.ts; evaluate reuse for terminal styling.
Activity
✨ Render written Markdown in Sidekick chat and entry Output (#1342)
🐛 Keep fence payload and written blank-line spaces in Markdown display (
♻️ Read written REPL Markdown with Lezer and reuse unchanged bodies (#…
🐛 Keep deeply nested Markdown emphasis literal (#1342)
🐛 Count escaped emphasis using the written marker run (#1342)
Render Markdown in Sidekick and REPL Output (#1351)