History is lost

[FrenchBen]

Dupe Check

• [X] I have searched Warp bugs and there are no duplicates

Describe the bug

Despite history files existing, several shell env changes, history in Warp isn't retained. The question then is: Where is the actual history preference set within Warp?

To reproduce

1. Use wap
2. Execute several "similar" commands like curl ...
3. Expect warp to recall older curl commands

Expected behavior

Warp should remember everything since the beginning of time :)

Screenshots

No response

Operating system

MacOS

Operating system and version

14.5

Shell Version

zsh 5.9

Current Warp version

v0.2024.07.16.08.02.stable_03

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 an issue only in Warp?

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

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[FrenchBen]

Not only is history from Zsh not respected, the history written to the HISTFILE isn't shared across tabs or pane, rendering cross-tab functionality painful.

Replicate bug

1. Create 2 tabs (or pane)
2. Type something
3. Try to get the history of what you typed from another pane

Histfile will show the command:

yet Warp cannot "find it"

[dannyneira]

Hi @FrenchBen sorry to hear about this. Warp doesn't share history immediately across sessions, although this setting may be enabled in your zsh config. Currently, Warp does read the HISTFILE upon loading a new session, so any commands you ran in other sessions should show up when you open a new window/tab/pane.

[FrenchBen]

@dannyneira thank you for your note - How does Warp save its history if not written to the HISTFILE directly, which would make it cross-session? Is this an issue of the history being written, but Warp not re-loading it?

[dannyneira]

How does Warp save its history if not written to the HISTFILE directly, which would make it cross-session?

Yes they are written to the HISTFILE as with normal terminals, but the history doesn't get consolidated across existing sessions (regardless of rc file settings), they only get combined when a new session is made.

Is this an issue of the history being written, but Warp not re-loading it?

Warp does reload the history and consolidate it, on new sessions only. I believe there is a feature request for option to consolidate on current sessions, or respect rc file settings for consolidation of history, but this isn't an option yet.

[FrenchBen]

@dannyneira I noticed a few warp_ shell functions. Would a reload shell script be the right place to do this (aka launch warp_hist or similar)? How would I go about creating a feature design discussion? Can you point me to the code that loads / consolidates history on new session?

[dannyneira]

Not sure of which code exactly does this, but starting a new session will consolidate the history as far as I'm aware you can't workaround or disable this behavior

[tzaffi]

Does anyone have a workaround? For me this is borderline blocking me from using Warp.