Hi @grizzled scarab. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Fix documentation regarding auto-warpifying subshells
latent knotBOT
Thank you for bringing this to our attention. You're correct that the documentation regarding auto-warpifying subshells needs to be updated, especially for SSH connections on Windows.
Based on your experience, it seems that for SSH connections from Windows Warp Terminal to a Debian 12 server using bash, the auto-warpify command needs to be added to the ~/.profile file instead of ~/.bashrc or ~/.bash_profile.
The current documentation in Warp's Subshells feature page suggests adding the command to ~/.bashrc or ~/.bash_profile for bash subshells. However, your solution of adding it to ~/.profile is correct for SSH login shells, as ~/.profile is executed for login shells, which is typically the case for SSH connections.
Your .profile file configuration is correct, and it's good that you've placed the auto-warpify command at the end of the file:
# Auto Warpify
printf '\eP$f{"hook": "SourcedRcFileForWarp", "value": { "shell": "bash"}}\x9c'
This issue should be reported to the Warp development team so they can update the documentation to include this information for SSH connections, especially from Windows. You can submit this as a documentation improvement issue on the Warp GitHub Issues page.