-
Notifications
You must be signed in to change notification settings - Fork 602
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
Tab completion for file/directory arguments doesn't work for commands that Warp doesn't recognize natively (e.g., zed, mate, code, subl), unless an explicit path prefix like ~/ is provided.
To reproduce
Open Warp terminal
Navigate to any directory: cd ~/Documents
Type zed (with space) and press TAB
Expected: List of files/directories in current directory appears
Actual: Nothing happens, or only recently used files are shown
Workaround that works:
zed ~/ + TAB → shows files (but starts from home, not current directory)
Open a zsh subshell (zsh command), then zed + TAB → works correctly
What I've tried (none of these fixed it):
Added compdef _files zed mate code subl to .zshrc
Switched from Universal Input to Classic Input
Disabled Warp's intelligent autosuggestions
Modified keybindings.yaml
Various zstyle completion settings
Expected behavior
Warp should either:
Pass TAB completion to the shell for unrecognized commands, OR
Default to file completion for any command it doesn't have specific completions for
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
26.2.0
Shell Version
zsh 5.9 (arm64-apple-darwin25.0)
Current Warp version
v0.2025.12.17.17.17.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
Impact:
This breaks the standard terminal workflow for developers who use editors launched from command line. Having to type ~/ and navigate from home directory every time significantly slows down productivity.
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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