Skip to content

fix(web): keep lettered and bullet-character lines apart in assistant replies - #136

Merged
nullStack65 merged 1 commit into
release/native-0.1.10from
fix/clo-977-lettered-line-breaks
Nov 20, 2026
Merged

nullStack65 merged 1 commit into
release/native-0.1.10from
fix/clo-977-lettered-line-breaks

Conversation

@nullStack65

Copy link
Copy Markdown
Owner

Kameron saw a reply render as one solid block (Linear CLO-977, plain-English output for every model). The reply listed nine items as "A. …", "B. …" on separate lines. Markdown has no lettered lists, and CommonMark joins single newlines into one paragraph, so T3 showed the nine items as one run-on paragraph.

What changes

Assistant messages now keep their line breaks when two or more consecutive lines start with a letter marker (A., b), (c)) or a bullet character (•). Fenced code is ignored. The check extends shouldPreserveAssistantLineBreaks, which already turns on the existing remark-breaks plugin for "★ Insight" blocks. Search highlighting (threadFindText) uses the same function, so it stays consistent.

Trade-offs

  • In a message that trips the check, every soft newline becomes a line break, not only the lettered ones. Assistants rarely hard-wrap prose, so this should be invisible in practice. A message that both hard-wraps prose and uses lettered lines will show the wrapped lines as written.
  • Real markdown lists, lettered items separated by blank lines, and a single lettered line keep today's rendering.

Other options considered

  1. A remark plugin that breaks only before marked lines. More precise, but it adds a new plugin to the shared pipeline for a case the existing remark-breaks path already handles.
  2. Turn on remark-breaks for every assistant message. Simplest, but it changes rendering for any provider that hard-wraps its prose.
  3. Fix only the writer side. The closura-agent-config change for the same Linear issue adds a copy linter that flags these lines. Models will still produce them sometimes, so the renderer should not punish the reader.

Verification

  • vp test run src/markdownPipeline.test.ts in packages/shared: 33 passed, including 9 new cases for the check and one that confirms break nodes appear once breaks are on.
  • vp test run src/threadFindText in packages/shared: 11 passed.
  • pnpm run typecheck in packages/shared: passed.
  • vp fmt on the changed files: applied.
  • Not run locally: vp lint. On this host Node 22 cannot load the repository's TypeScript oxlint plugin; CI runs it.
  • Not checked in a live client.

Model: claude-opus-5-5
Task: fix
Agent: claude-code (CLO-977)
Harness: t3/claude
Requirement: https://linear.app/closura/issue/CLO-977
Human review: not requested

Deploy: fleet

🤖 Generated with Claude Code

… replies

Markdown has no lettered lists. An assistant reply that wrote "A. …" and
"B. …" on consecutive lines rendered as one solid paragraph, because
CommonMark treats single newlines as spaces. Assistant messages now keep
line breaks when two or more consecutive lines start with a letter marker
(A. / b) / (c)) or a bullet character (•), outside code fences.

Model: claude-opus-5-5
Task: fix
Agent: claude-code
Lane: CLO-977

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@nullStack65
nullStack65 merged commit 23f4c06 into release/native-0.1.10 Nov 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant