Allow to have a separate shell command history for each windows and tab

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

The issue names no files, tests, or entry points. Start by locating Warp's command-history handling and how windows and tabs are identified, then determine how history is persisted across restarts. Done means each window and tab retains a separate command history without reverting to a shared history.

Written by the indexing model from the issue text.

Description

area:search area:window-tabs-panes enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?
I would love for Warp to solve my biggest wish I ever had since switching from Windows to MacOS some 10 years ago. I hate the shared shell command history and would love to have a separate command history in each windows and tab.
Especially when restarting Warp all tabs revert to the shared command history making it basically useless.
Is your feature request related to a problem? Please describe.
I find it incredibly frustrating to have a shared command history.
Additional context

No response

How important is this feature to you?

5 (Can't work without it!)

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.