warpdotdev / warpdotdev/warp

Input area loses focus after command execution, seemingly at random

Open
#3,729 10 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug ready-to-implement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Discord username (optional)

No response

Describe the bug

When entering any command (usually I'm just running git commands), often the input area loses focus after the command execution completes, and the input area must be manually reselected to continue executing additional commands.

The Warp window is still in focus (as Mac toolbar), but there is no active "section" and all subsequent key presses have no effect until one of the window sections is manually selected again.

Currently I only have one customisation:

  • Theme installed "Dracula"

There is no discernable pattern I have noticed:

  • occurs both when an error code is returned, or command is successful (exit code 0)
  • can occur on any type of git command
To reproduce
  1. $ git log
  2. select and copy SHA from log view
  3. $ git diff {file}
  4. command completes with git diff shown, and the input area has lost focus
  5. manually reselect

Again, this is not a reliable reproduction test.

Expected behavior

Maintain focus on Warp input area, unless focus was changed by the user during command execution.

Screenshots

No response

Operating system

MacOS

Operating system and version

Ventura 13.4

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0)

Current Warp version

v0.2023.09.26.08.09.stable_00

Regression

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

Recent working Warp date

No response

Additional context

If no one else is experiencing this issue then I'd be happy to close this and try some other things (upgrade OS etc)

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

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

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

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.

Research direction

No source files, tests, or entry points are named. Start by reproducing the git log/git diff sequence on macOS with zsh and observe focus after command completion; done means the Warp input area retains focus unless the user changes it.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, macos, zsh
Domain
cli, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.