#When using the where command no paths show up

2 messages · Page 1 of 1 (latest)

signal kelpBOT
#

Hi @open ocean. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Warp on Windows doesn’t currently support cmd.exe as a shell, and the where command is a built‑in from cmd.exe. On Windows, Warp officially supports PowerShell 7 (default), PowerShell 5, WSL2, and Git Bash, but not Command Prompt. [Supported shells]

So when you run where git inside Warp, you’re not actually in cmd.exe, and that built‑in command won’t behave as it does in Command Prompt (often resulting in “nothing happens”–style behavior similar to other Windows‑specific issues reported in the tracker). [Command not doing anything]

Given the current docs and issues, there’s no indication that Warp provides a direct replacement for cmd.exe’s where command. To get the behavior you see in Command Prompt, you’d need to:

  • Run that command in a real cmd.exe window, or
  • Use an equivalent in a supported shell (e.g., PowerShell’s Get-Command git), though this isn’t documented in the provided sources.

If you specifically need cmd.exe/where inside Warp, the knowledge sources don’t show a supported way to do that today.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: