You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(tui): make paste summary thresholds configurable #14712
The paste summary feature is genuinely useful when pasting large chunks of content — it keeps the prompt input clean and manageable. However, the current thresholds (3 lines / 150 characters) are too aggressive for those of us who use voice dictation software (e.g. Whisper Flow, Whispering, others) on a regular basis.
Dictated text frequently exceeds 150 characters in a single utterance, causing it to be immediately collapsed into `[Pasted ~1 lines]`. This makes it impossible to spot and correct the small transcription errors that dictation software occasionally makes — which is exactly the moment you most want to see what was pasted. This is the scenario described in #3949, where the only workaround offered was `experimental.disable_paste_summary: true` — a blunt hammer that trades one problem for another: you lose paste summaries entirely, which is painful when you then paste a 200-line config file or a stack trace.
What's needed is the ability to tune the thresholds to match your typical dictation length, so paste summaries kick in only when the content is genuinely large.
Both would be optional, defaulting to the current values (3 and 150 respectively), so existing behaviour is preserved for anyone who doesn't set them.
Prior art: PR #1960 attempted this with a nested config structure (experimental.editor.summary_thresholds); this proposal uses flat keys consistent with the existing experimental config style.
Activity
github-actions commentedon Feb 22, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:(current title usesfeat(tui):)Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Feb 22, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.
aspiers commentedon Mar 3, 2026
Resubmitted as #15767.
frederickfogerty commentedon Mar 19, 2026
The 2-hour window to fix issues according to the contributing guidelines is crazy 🤯