SSH Password Authentication Fails in Interactive Mode #8557
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
The interactive mode (mode: interact) consistently fails to correctly enter passwords for SSH authentication, resulting in "Permission denied" errors even when the correct password is provided.
To reproduce
- Use run_shell_command with mode: interact
- Attempt SSH connection with password authentication: ssh user@host
- Provide correct password in interact_task instructions
- Observe authentication failure after multiple attempts
Expected behavior
The interactive subagent should successfully enter the password when prompted by SSH, allowing successful authentication.
Actual Behavior:
• SSH prompts for password 2-3 times
• Each attempt results in "Permission denied"
• Connection fails with exit code 255
• Error message: "Permission denied (publickey,password)"
Screenshots, videos, and logs
franz@192.168.10.163's password:
Permission denied, please try again.
franz@192.168.10.163's password:
Permission denied, please try again.
franz@192.168.10.163's password:
franz@192.168.10.163: Permission denied (publickey,password).
Operating system (OS)
macOS
Operating system and version
26.2.0
Shell Version
zsh 5.9
Current Warp version
v0.2026.01.28.08.14.stable_04
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
Environment:
• Warp version: Latest (tested on 2026-02-02)
• OS: macOS
• Shell: zsh 5.9
• SSH server: Debian (tested with server 192.168.10.163)
On older war it was working without any problem.
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