Execute command for a previous block

Discord username (optional)

No response

Describe the solution you'd like?

I'd like to be able to select a specific block and have its output piped as input to a new command.

Is your feature request related to a problem? Please describe.

I usually find that there is something in a command's output that I'd like to parse after the fact.

In most cases, I don't want to (or can't) run the command again (e.g. if the command isn't idempotent then running it again isn't possible, such as creating or deleting a bunch of infrastructure resources).

Ideally, when running the command I'd use tee to keep a copy of the output, but realistically that doesn't happen very often, and a lot of times I'm executing commands and scripts and it's not until after wards I think "hmm, I could do x y and z data processing with that".

But I don't want to have to manually copy the output and stick it into a file (as that is very tedious, and then I have to do clean-up for the file afterwards etc) just to do a:

cat file | my_new_pipeline_of_things

I'd love it if I could just do something like:

<ref_to_block> | my_new_pipeline_of_things

Where <ref_to_block> is something simple and short to type like #N where N is the number of blocks back to grab the output from (obviously # is reserved for AI stuff so it'd have to be some other character) and then the UI part of the terminal could give me a right-click context menu option to "copy reference to block" which would auto-magically insert the right <ref_to_block> at the start of my prompt so I can immediately do my piping.

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

The issue names no files, tests, or entry points. Start by locating the terminal block output and context-menu entry points; done means a selected prior block can be referenced as input to a new command without rerunning the original command or manually copying its output.