Command History Blocks Recent Command Output

Discord username (optional)

No response

Describe the solution you'd like?

I'd like to be able to recall recent commands using the up arrow without 5 rows of command history blocking my view of recent command output in the terminal. Currently it seems like there is no way to view the command history and last lines of the most recent command output at the same time.

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

With warp's current behavior, I can't modify my most recent command to address typos, etc. based on error messages/output from my most recent command execution. Warp's behavior prevents me from quickly fixing mistakes. This departs from my expectations based on years of CLI usage - normally you can press the up arrow to recall your most recent command and edit it in-place while viewing the most recent command output to see where you made a mistake.

Additional context

Here's a few options that would resolve this issue:

• add the ability to disable warp's command history functionality and allow default shell behavior - in my experience this means start by recalling the most recent command to the prompt, each up arrow press recalls the next command down the history
• create a way to display history without overlaying it on top of command output. This could look like adding a way to specify the number of lines of history to display, or presenting the overlay on top of the prompt rather than command output blocks
• create another input position mode that handles the prompt like 'pin to the top' by having the command prompt pinned to the top of the window, but displays command output like 'pin to the bottom'.
• implement a context-aware capability to scroll past the bottom of the command output block while there is a command history overlay displayed.

Here's an example. it doesn't fully capture how aggravating this is because you can see the typo over the history overlay, but I hope it demonstrates enough - there's no way to see the last lines of output while the command history is displayed. Since there's no way to recall commands and view the last few lines of output at the same time (command search is an even bigger overlay) I have to give up on my previous command and re-type it again if I want to view the last reported error while I'm fixing my command.

How important is this feature to you?

5 (Can't work without it!)

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

None

Start by reproducing the command-history overlay with the up arrow and compare it with the most recent command output. Determine which interaction best allows both command editing and viewing the latest output, then verify that the chosen behavior addresses the listed use case without obscuring the error output.