A configuration option to ignore injecting SSH Wrapper for certain connections/domains

Dupe Check

• I have searched Warp feature requests and there are no duplicates

Describe the solution you'd like?

Would it be possible to add a configuration option to Warp which would allow specifying connections or domains for which the SSH Wrapper will not be injected into the connection?

Possibly something like an ignore list which Warp would check before trying to execute the SSH Wrapper script on the remote machine?

Is your feature request related to a problem? Please describe.

Currently it is only possible to either have the SSH Wrapper functionality enabled or disabled in Warp.

When SSH Wrapper is enabled it will cause connection issues if the remote server does not allow exec system calls.

This is especially inconvenient when accessing enterprise-grade configurations (PaaS, SaaS) which have very strict connection rules.

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

No files or tests are identified in the issue. Start by locating the SSH Wrapper injection path and the existing enabled/disabled configuration, then trace how connection or domain targets are represented. Done means specified targets skip wrapper injection while other connections retain current behavior, with coverage for both cases.