Skip to content

feat(tui): make paste summary thresholds configurable #14712

Closed as not planned
Closed as not planned

Description

@aspiers

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.

Proposed config:

```json
{
"experimental": {
"paste_min_lines": 6,
"paste_min_length": 500
}
}
```

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

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Feb 22, 2026
  2. github-actions commented on Feb 22, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • Feature request issues must have a title starting with [FEATURE]: (current title uses feat(tui):)
    • Feature request issues must include the verification checkbox confirming the feature hasn't been suggested before

    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.

  3. github-actions commented on Feb 22, 2026

    @github-actions
    Contributor

    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.

  4. aspiers commented on Mar 3, 2026

    @aspiers
    ContributorAuthor

    Resubmitted as #15767.

  5. frederickfogerty commented on Mar 19, 2026

    @frederickfogerty

    The 2-hour window to fix issues according to the contributing guidelines is crazy 🤯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

needs:complianceThis means the issue will auto-close after 2 hours.opentuiThis relates to changes in v1.0, now that opencode uses opentui

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions