fix: output HUD as plain text to prevent TUI rendering buffer collisions#72
Conversation
ANSI dim codes (\x1b[2m/\x1b[22m) caused the TUI renderer to miscalculate text positions, producing garbled output where response text fragments mixed into the HUD line. Removing all ANSI codes from the HUD output eliminates the rendering buffer collision. HUD strip regex now uses pattern-based matching (pipe-separated percentage and day window) instead of ANSI code anchors.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (3)
✨ 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 |
Summary
\x1b[2m/\x1b[22mdim wrapper)Root Cause
ANSI dim codes caused the TUI renderer to miscalculate text positions during the transition from streaming deltas to final text. Response text fragments appeared garbled within the HUD line (e.g., "Sisyphus can |", "clau neede-opus-4-6").
Test