SSH host completion drops hosts when ~/.ssh/config uses a Windows drive-letter `Include` path

[maxmilian]

Link to @sesa501225's main issue: warpdotdev/warp#9417

The ssh host-completion generator (SSH_CONFIG_CMD in command-signatures/src/generators/common.rs) expands Include directives with an awk program that prefixes any path not starting with / with $HOME/.ssh/. A Windows drive-letter path such as Include C:\Users\me\.ssh\extra_config (written by Git Bash users who pick Windows ssh.exe at install) therefore becomes $HOME/.ssh/C:\Users\…, which does not exist — so the included hosts never appear in completion.

Fix proposed in #280 (normalize C:\… / C:/… to MSYS/Git Bash /c/… form before the relative-path branch).

[oz-for-oss]

@maxmilian

Here's what I found while triaging this issue:

This appears to be a real parsing gap in SSH host completion for Git Bash/MSYS-style environments. A proposed fix is already open in #280.

Maintainer details

I concluded that SSH host completion appears to drop hosts from included config files when the Include path is written as a Windows drive-letter path..

Triage summary

This looks like a valid bug in SSH host completion for environments where ~/.ssh/config contains an Include directive with a Windows drive-letter path. The current shared SSH host generator reads ~/.ssh/config, extracts Include paths with awk, expands ~, and treats only paths starting with / as absolute. As a result, C:\Users\... or C:/Users/... include paths are classified as relative and prefixed with $HOME/.ssh/, so hosts defined in those included files are not read.

Reproducibility

High. The behavior follows directly from the current generator command and the report gives a concrete path shape that exercises the failing branch.

Likely root cause

command-signatures/src/generators/common.rs defines SSH_CONFIG_CMD, which is reused by the SSH and SCP generators. Its awk logic does not recognize Windows drive-letter absolute paths before applying the relative-path fallback. The adjacent generator registration files are relevant because ssh and scp both consume common::ssh_hosts_generator().

Duplicate check

I checked all open non-PR issues in warpdotdev/command-signatures excluding #282, plus recently closed issues from the last 7 days. No qualifying duplicate set was found.

Related work

PR #280 is already open with a proposed fix for this issue, but it currently has requested changes.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz