Warp should keep the shell session alive across app updates

Open
#3,647 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the issue with a continuously running stdout process, then click the Update Warp button and observe the restored tab. Trace how the app restart reconnects previously open tabs to their shell sessions; done means process output continues in the original tab after an update restart.

Written by the indexing model from the issue text.

Description

area:shell-terminal bug ready-to-implement triaged
Discord username (optional)

confident_parrot_17725

Describe the bug

I have a process running in a warp tab which is writing to stdout that I am watching.
When I clicked on the Update Warp button, warp restarted and the process is still running, but I am no longer getting its output to the tab where it was running

To reproduce
  1. start a process that continuously writes to stdout
  2. click the Update Warp button
  3. warp restarts and keeps all its previously open windows and tabs, but you no longer get the process' output
Expected behavior

Tabs that were receiving process output should continue to do so after warp restarts on update.

Screenshots

No response

Operating system

MacOS

Operating system and version

macOS Ventura 13.5.1 (22G90)

Shell Version

GNU bash, version 3.2.57(1)-release (arm64-apple-darwin22)

Current Warp version

v0.2023.09.06.18.09.stable_00

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 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

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.