Composer: persist long pastes as per-conversation attachment chips - #89
Conversation
Pasting a stack trace, a log, or a page of code into the composer buries the input: the textarea grows to its cap, the send button drifts away, and what you were writing scrolls out of sight. Past ~900 characters or 12 lines, a paste becomes a chip above the input instead — the first lines fading out, the size beside them, an x to drop it. Shorter pastes are untouched and still land as text. On send the chips fold back into the message as <pasted-text> blocks: tagged rather than fenced, because pasted code and markdown carry fences of their own and nesting them loses the boundary. Nothing crosses the server, so every driver still receives a plain prompt. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0197wYuWWpF21iBeNgHZ8n3X
Three from review: - the send control keyed off typed text alone, so a chip on its own could only be sent with Enter — the mouse got a microphone instead - the remove button used `hidden` until hover, which took the only way to drop a chip out of the keyboard's reach; opacity plus focus-visible keeps the same look and puts it back in the tab order - the chip labelled UTF-16 code units as bytes, reading a third under on accented text. Measured in UTF-8 now, once at paste time rather than on every re-render Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0197wYuWWpF21iBeNgHZ8n3X
|
Warning Review limit reached
Next review available in: 13 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 Plus Run ID: 📒 Files selected for processing (6)
Comment |
2 participants
Integrates #68 with the per-conversation draft and approval/dictation behavior now on
main.Local verification: 204 tests passed (7 platform-specific skips), typecheck, Electron syntax checks, and production build.
Closes #68