Repository navigation
fix(terminal): stop fragmenting Claude chat words - #104
Conversation
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughUpdates terminal transcript wrapping to break at word boundaries, adds coverage for content preservation, and records W1-R6 renderer investigation, validation, rollout, and diagnostic guidance. ChangesTranscript wrapping
W1-R6 renderer records
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/dashboard/src/components/terminal/transcriptFormatter.ts`:
- Around line 149-154: Update the segment-boundary scan in the transcript
formatting logic to include candidate === start and handle a whitespace
delimiter at that boundary separately, consuming it when no later delimiter is
available so words are not split. Add a regression test for wrapping “word word”
at width 4, asserting the exact resulting content.
In `@tasks/2026-07-22-android-terminal-daily-driver-log.md`:
- Line 31: Update the final sentence in the daily driver log to use the
canonical lowercase “agentd” spelling, while preserving the rest of the entry
unchanged.
In `@tasks/2026-07-22-android-terminal-daily-driver-status.md`:
- Line 31: Keep renderer rollout status separate from painted-surface
acceptance: in tasks/2026-07-22-android-terminal-daily-driver-status.md lines
31-31, replace “defect fixed” with wording that the candidate fix is deployed
and painted-surface verification is pending; in
tasks/2026-07-22-android-terminal-daily-driver-metrics.jsonl lines 37-38, limit
pass statuses to implementation/deployment and mark root-cause confirmation or
live visual verification as pending.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: da792519-8fe7-4fd8-b743-e529a72183b6
📒 Files selected for processing (6)
apps/dashboard/src/components/terminal/transcriptFormatter.test.tsapps/dashboard/src/components/terminal/transcriptFormatter.tstasks/2026-07-22-android-terminal-daily-driver-log.mdtasks/2026-07-22-android-terminal-daily-driver-metrics.jsonltasks/2026-07-22-android-terminal-daily-driver-status.mdtasks/lessons.md
Summary
Root cause
The reported two-character artifacts were on the custom Claude chat history overlay, not xterm. Its estimated-column formatter split words such as
reportintorepor/t, making the suffix look like a changing artifact at the left edge while copied text remained correct.Verification
Production painted-surface verification will follow the automatic Coolify deployment.
Summary by CodeRabbit
New Features
Bug Fixes