Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

When using AWS terminal commands, the current input screen scrolls up and disappears. Specifically, when running a command like

aws configure sso

the terminal scrolls to the top, causing the input prompt to disappear instead of staying on the screen.

Even after configuring it to output from the top down, the same scrolling issue occurs.

To reproduce

Environment

• App: Warp Terminal
• Current Configuration: Tested with both "Start at the top"(Settings > Appearance > Input position) enabled and disabled.

Steps to Reproduce

1. Open the Warp terminal.
2. Ensure the setting to display output from the top is active.
3. Run an interactive AWS CLI command, such as aws configure sso.
4. Observe the terminal behavior during the command execution.

Expected behavior

Expected Result

• The input prompt and command output should remain visible within the current block or screen area.

Actual Result

• The screen automatically scrolls up, pushing the current input/output block out of view. This issue persists regardless of whether the "Start prompts at the top" setting is enabled or disabled.

Screenshots, videos, and logs

Running aws configure sso triggers a scroll issue (marked in red). The terminal stays locked to the bottom of the output, preventing me from seeing the active input state even as I continue typing.

Operating system (OS)

macOS

Operating system and version

26.3.1

Shell Version

zsh 5.9 (arm64-apple-darwin25.0)

Current Warp version

v0.2026.04.01.08.39.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None