Repository navigation
Conversation
Sidekick conversation bodies and the selected entry's rendered Output share a private display path over the pinned Marked lexer: headings, emphasis, list markers, link labels and code are styled runs, fences stay literal line for line, and unsupported constructs read as written. Controls are made inert before lexing and on every run. Retained text and raw reads are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#1342) A fence-like line closes only a fence opened with the same character and no longer run; a shorter or different run stays code. Lines written between blocks are drawn as written, so a whitespace-only line keeps its spaces. The spec states that formatting draws exactly the body its owner supplies.
Owner
Author
Independent reviewReviewed commit Verdict CHANGES REQUIRED Reviewer SummaryFindingsBlocking Blocking Non-blocking Non-blocking Non-blocking Non-blocking |
2 tasks done
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
REPL UI evidence
Mounted typing latency
Viewport 200 × 52. Milliseconds from character dispatch to the completed emulator write containing the changed Message value.
Why
Markdown in Sidekick messages and executed round Output appears as raw punctuation. This makes headings, links and code harder to scan in the terminal.
What changes
Both views use the same terminal formatting for headings, paragraphs, emphasis, lists, descriptive link labels, inline code and fenced code. The display wraps to the pane width and preserves the indentation and line breaks of code. The saved Markdown remains available through the existing raw readers.
How to verify it
Run the mounted Sidekick journey and the executable Markdown ReplBench journey in a prepared worktree. They exercise conversation text and round Output at wide and narrow sizes, including literal code, retained links and reopening. The paired evidence records the same fixture on
mainand this draft.Closes #1342.