#Command history is not shared between tabs (even when using Zsh).
7 messages · Page 1 of 1 (latest)
Hi @gaunt river. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Warp does not currently support real-time sharing of command history between tabs, panes, or sessions—even when using Zsh with options like setopt SHARE_HISTORY or setopt INC_APPEND_HISTORY. This is a known limitation and is different from the behavior you may see in other terminals like iTerm2 or the VSCode integrated terminal, where history can be shared live between sessions.
How Warp handles history:
- Warp reads your shell history file (e.g.,
~/.zsh_history) only when a new session (tab, pane, or window) is started. - Commands entered in one tab will not appear in the history of another tab until you open a new session.
- Zsh options such as
SHARE_HISTORYandINC_APPEND_HISTORYdo not enable real-time history sharing in Warp, even though they work in other terminals. This is a limitation of how Warp manages session history internally, not a shell configuration issue History from other terminals/sessions not synced to warp's history and vice versa Shared history accross sessions Comand history is the same for all tabs.
Is this a bug?
- This is not considered a bug by the Warp team, but rather a current design limitation. There is no configuration or setting in Warp that enables real-time, cross-tab history sharing at this time.
- Many users have requested this feature, and it is being tracked as a feature request. The Warp team is aware that this is an important workflow for many users, but as of now, there is no built-in solution or workaround other than restarting or opening a new session to reload history History from other terminals/sessions not synced to warp's history and vice versa History is lost.
Summary:
You are not missing a configuration—Warp simply does not support live, shared command history between tabs or panes at this time. If this feature is indispensable to your workflow, you may want to follow or upvote the relevant feature requests on Warp's GitHub to signal its importance to the developers.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@gaunt river Kapa.ai is still learning and improving, please let me know how I did by reacting below.
Ok, this is in the documentation: https://docs.warp.dev/terminal/entry/command-history
To be frank, I don't understand how the decision to get rid of such an important feature could be made for a premium terminal application.
The history is consolidated when the tab/pane is closed and a new one is opened, but not by default in all sessions.
There is request to support this feature https://github.com/warpdotdev/Warp/issues/3422
(note that many shell features need to be supported in Warp since its a wrapper around the shell, i.e. vim mode which we do support)