zsh:51: command not found: zsh when trying to ssh
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 65.1k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Description
Discord username (optional)
No response
Operating System
MacOS
Operating System and Version
macOS 14.2 Beta (23C5047e)
Local Shell Version
5.9.0.1-dev
Remote Shell Version
5.9
Warp Version
v0.2023.11.14.08.02.stable_02
I have tried commenting out my system & user rcfiles and warp still will not bootstrap
- Yes
Screenshots
Include shell xtrace output
WARP_DEBUG_MODE=1 ssh Server
HermesChen@(my server)'s password:
zsh:51: command not found: zsh
Connection to (my server) closed.
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:e7dfaa84-5fdb-4a00-b754-d8912da923fa
None
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported failure with WARP_DEBUG_MODE=1 ssh Server on macOS, comparing it with another terminal and reviewing the included shell xtrace output. The report names no source file or test; done means SSH no longer closes with “zsh:51: command not found: zsh” in Warp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, zsh
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100