Keep latest stdout near input box

Open
#3,193 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli, desktop

Research direction

No files, tests, or entry points are named. Start by locating the terminal layout code that positions the CLI input and stdout when input is configured at the top; done means the newest stdout remains visible near the top while older output moves below it without requiring downward scrolling.

Written by the indexing model from the issue text.

Description

enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?
- If I place my CLI input box at the top in my settings, the input box stays at the top
- This is great and ergonomic, but the latest stdout is pushed to the bottom of the screen
- This requires me to have to always scroll down to find the latest stdout
- You should keep the latest stdout at the stop, and push old stdout down
- This would allow users to pin the input box to the top, and keep their latest stdout where they can see it
Is your feature request related to a problem? Please describe.
- Looking "down" at the CLI input box is bad ergonomics (terrible for your neck and back)
- I love <3 that Warp gives me the option to put the input at the top - much better on my neck
- However, I still end up having to scroll down to find my latest stdout (bad devx)
- If the latest stdout could stay near the top, that would be amazing!
Additional context

No response

How important is this feature to you?

4

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

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.