Autocomplete Fails to Recognize Binaries from Dynamically Updated PATH in Warp

Discord username (optional)

No response

Describe the bug

I am experiencing an issue with Warp's autocomplete feature where it fails to recognize binaries from a dynamically updated PATH environment. It occurs when I activate some micromamba/conda environment which updates PATH, or basically any workflow in which you update the PATH variable in the same shell.

The most annoying thing is warp shows "red twiggle" beneath the binary i am trying to execute even though it's present, and it should ideally show it as green.

To reproduce

1. Open a warp shell.
2. Change the PATH variable to include a new directory.
3. type a binary present in the new PATH - the autocompletion menu will fail to detect this newly found binaries.
4. It will also show a "red twiggle" beneath the binary, while infact it should be green as it's present in PATH

Expected behavior

Autocompletion should work even when the PATH variable is updated.

Screenshots

No response

Operating system

MacOS

Operating system and version

14.4.1

Shell Version

zsh 5.9 (aarch64-apple-darwin23.4.0)

Current Warp version

v0.2024.04.09.08.01.stable_01

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?

Yes, this issue prevents me from using Warp daily.

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:b9d78064-c89e-4973-b153-5178a31ee54e

None

The report names no implementation files or tests. Reproduce in a Warp shell on macOS with zsh by changing PATH, then trace the autocomplete command lookup entry point; done means binaries added after the update are recognized and no longer marked with a red squiggle.