SSH Connect Timeout Configurable

What variant of Codex are you using?

App

What feature would you like to see?

Codex Desktop currently seems to use a fixed SSH ConnectTimeout for remote connections. In my setup, the effective timeout is too short and causes connection failures for hosts that do eventually connect successfully.

This shows up most often when the SSH path includes things like:

• ProxyCommand
• ProxyJump
• bastions
• VPN startup
• remote brokers such as coder ssh
• waking a remote workspace before it becomes reachable

A fixed timeout around 10 seconds is too aggressive for these cases. Regular SSH often succeeds if given 15-30 seconds.

Requested change

Please make the SSH connect timeout configurable in Codex Desktop.

Ideally:

• expose it as a user setting
• support a global default, and optionally per-host overrides
• respect ~/.ssh/config where possible, or provide a Codex-specific override if Codex must pass explicit SSH flags

Example

A timeout of 30s would already be much more practical than the current fixed behavior in environments where the first connection can legitimately take longer.

Additional information

_No response_