[FEATURE]: Allow to expand the pasted text (e.g. [Pasted ~1 lines]) #8501

This issue might be a duplicate of existing issues. Please check:

• Pasted text from a clipboard is shown as "[pasted #2 1+ lines]" instead of inline pasting #3532: Pasted text from a clipboard is shown as "[pasted Roadmap & Existing Issues #2 1+ lines]" instead of inline pasting
• Fix TUI paste editor regression - pasted text object not expanding in editor #3484: Fix TUI paste editor regression - pasted text object not expanding in editor
• Support paste summary collapsing #416: Support paste summary collapsing
• Why lowered paste summary? #3949: Why lowered paste summary?
• Pasting text in WezTerm on X11 Ubuntu always results in [Pasted ~X lines] #5687: Pasting text in WezTerm on X11 Ubuntu always results in [Pasted ~X lines]

Feel free to ignore if none of these address your specific case.

Hi @rekram1-node, what does the team think about this?

I would love this. Also using text to speech a lot.

@rekram1-node, any updates?

Been wanting this for a long time. At this point, I'll just submit my query, immediately interrupt, and then /undo, just so I can see my speech-to-text output.

@berenar thanks for suggesting this! I think enabling adding a keybind as done in PR #8496 looks really cool. That said, it pollutes the keybinds for a relatively small benefit.

A simpler discoverable solution may be to support an additional selected state to the pasted summary block.

Instead of skipping over the pasted block when moving your cursor towards it, this can make it appear highlighted.

When you are currently on a highlighted paste summary block,

• moving left or right moves your cursor past it, deselecting it
• pressing Enter expands it in-line, replacing the block with the raw pasted text
• backspace/delete deletes block

I don't think there'd be too much of a need to track the pasted block state and support collapsing it, although adding that support as done in #8496 in the future is always an option.

Created opentui#652 to optionally customize the extmark's handling of the cursor, allowing behaviors like selecting an extmark rather than only skipping over it. If that's accepted, implementing this in opencode is trivial (see packages/core/src/examples/extmarks-demo.ts in opentui for example).

I really need this.

I really need this

I also really need this

This is one of the most frustrating things I have ever encountered. I don't know how on earth seeing "Pasted +1 lines" makes sense to anyone. Absolutely ridiculous. What makes it worse is that you can't even click on it to expand it, to edit or even view. What on earth are you thinking guys!

+1

I would love the expand feature as well. Too many times I want to modify the pasted text for the prompt.

How about just by clicking on the "pasted lines" placeholder? No toggle. Once expanded, stays expanded. Just my two cents.

How about just by clicking on the "pasted lines" placeholder? No toggle. Once expanded, stays expanded.

+1 that's all I really want or need

I'm using wispr dictation to type, which uses paste for longer text. It's also not usually perfect on the first shot, so I need to edit. Having opencode take 2 sentences and put it in the pasted text block such that I can't easily edit it is a huge turn-off and I may switch to another AI CLI just because of this.

This is my #1 pain point with OpenCode CLI.

In Claude CLI, double-pasting automatically expands the [Pasted... ] block - why not use the same convention?

I worked around this by simply disabling the summary and always paste the whole text. See #21315 (comment).

Claude code does this by double pasting (cmd/ctrl+v+v: You paste with ctrl/cmd modifier, and while holding the modifier, press the v key again and it expans to the raw text for that paste). I like that approach personally, and feels natural.

@sdivens it's not the same and I believe does not cover the requirement. I may want to extend only one paste. A prompt may consist of multiple big pastes.

Oh and, it's already enabled:

Any update on this? This is a feature I miss the most from Claude Code

It seems there's no real consensus in how this feature should be implemented which is the main blocker. Maybe we need to summarize the approaches people have suggested so far alongside with up/downsides and requirements? I'm a bit short on time though.

I have a proposed implementation #41813 check the preview to see how it looks toggled/untoggled.