clear command

[adrianov]

Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

As a Linux user, I’ve grown accustomed to using the clear command to wipe the output so I can scroll to the top and read the next command in full. Warp doesn’t truly support this—previous outputs remain in the window. Could you make it respect the clear command? When reading git diffs, manual scrolling makes it easy to skip the start of the latest diff. I know the 'scroll to top' feature exists, but it isn’t quite the same—I think you’d understand.

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

No response

Additional context

No response

Operating system (OS)

Linux

How important is this feature to you?

5 (Can't work without it!)

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

[oz-for-oss]

@captainsafia

You can view the triage session on Warp.

Here's what I found while triaging this issue:

• Warp currently handles clear with a Warp-specific screen-clear behavior that preserves prior terminal blocks/scrollback rather than deleting previous output.
• This looks like a terminal output enhancement request, not a Linux-specific installation problem.

Maintainer details

I concluded that feature request to change Warp's clear semantics so previous blocks/scrollback are not left visible before the next command output..

Automated triage

Summary: Feature request for clear to behave more like a traditional terminal clear/scrollback boundary so the next command's output can be read from the top without older Warp blocks remaining in the same scroll context.

Observed symptoms: The reporter runs clear before commands such as git diff, then wants the latest command output to start from a clean top-of-scroll position. They report that Warp keeps previous outputs accessible/visible, which makes manual scrolling likely to skip the beginning of the latest diff.

Classification: Enhancement request for terminal output/block-list behavior, not a confirmed regression. The issue was filed through the feature request template and describes desired clear semantics rather than a crash or broken command execution.

Code evidence:

• app/assets/bundled/bootstrap/bash_body.sh, zsh_body.sh, and fish.sh redefine clear to send a Warp Clear hook; app/assets/bundled/bootstrap/pwsh.ps1 does the same for clear and Clear-Host.
• app/src/terminal/model/ansi/dcs_hooks.rs defines ClearValue as the shell hook payload.
• app/src/terminal/model/terminal_model.rs handles that hook by calling clear_visible_screen().
• app/src/terminal/model/blocks.rs implements clear_visible_screen() by removing old gap items and inserting a gap around the active block while preserving the existing blocks, which matches the reporter's observation that prior output remains available.
• app/src/terminal/model/grid/ansi_handler.rs separately handles ANSI CSI J clear modes; the block-list layer also has a TODO around ClearMode::All, suggesting the standard terminal clear path and Warp's custom block-list clear semantics are intentionally separate today.

Reproducibility: High from code inspection and the described workflow. No exact Warp version is needed for initial routing, though a future implementation/spec may still decide whether the desired behavior should delete prior blocks, hide them, reset scroll position, or introduce a configurable clear mode.

Duplicate check: No likely duplicates were found in the provided recent/open issue list.

Suggested routing: area:shell-terminal; involve shell bootstrap and terminal block-list owners.

Follow-up needed: None for initial triage.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[Dnreikronos]

I will work on this!

[Dnreikronos]

Hi, @captainsafia!!!
Can someone assign this issue on me?

[captainsafia]

@Dnreikronos Thanks for your enthusiasm! We want to clarify one thing with the original bug reporter before we pursue this.

@adrianov Can you verify if agent's note above makes sense? Warp does support the clear command. Can you record a video of what you're seeing happen with it that doesn't align with expectations.

[Dnreikronos]

@Dnreikronos Thanks for your enthusiasm! We want to clarify one thing with the original bug reporter before we pursue this.

@adrianov Can you verify if agent's note above makes sense? Warp does support the clear command. Can you record a video of what you're seeing happen with it that doesn't align with expectations.

I can reproduce that locally too:

https://github.com/user-attachments/assets/0c0fb8d9-8d90-4374-911d-ec9c60d9dc41
And I think that this behavior that we have on the stable version now it's not the best one....it's a little strange to clear the terminal, scroll above and still see everything there.

[adrianov]

@Dnreikronos @captainsafia Yes, just like that. Thank you

[dannyneira]

Warp's current clear basically fills the current view with blank space, retaining the ability to scroll and still see session history. This is also how clear works in iTerm2, Mac Terminal, and Kitty. Other terminals like Ghostty, delete the session history entirely, so I think it depends on the terminal how clear works exactly.

As a stopgap, Warp does have CMD+K on Max (CTRL+SHIFT+K on Windows | Linux) to delete the blocks in the current sessions, which functions like how you expect clear to work (deleting everything in the current session history).

[zachlloyd]

we could also make this configurable behind a setting. that would be very easy if it would solve the issue