codex - 💡(How to fix) Fix SSH Connect Timeout Configurable [2 comments, 1 participants]

TL;DR

Making the SSH connect timeout configurable in Codex Desktop is likely to resolve connection failures due to the current fixed timeout being too short.

Guidance

• The current fixed SSH ConnectTimeout in Codex Desktop may be too aggressive for certain setups, causing connection failures.
• To mitigate this, consider using a longer timeout, such as 15-30 seconds, which is often successful in regular SSH connections.
• A configurable timeout, either as a global default or per-host override, would allow users to adapt to their specific environment needs.
• Respecting ~/.ssh/config or providing a Codex-specific override could also help in achieving a more flexible connection setup.

Example

No specific code example is provided as the issue focuses on a configuration change rather than a code modification.

Notes

The exact implementation details of making the SSH connect timeout configurable are not specified, and it may require changes to Codex Desktop's settings or underlying SSH connection handling.

Recommendation

Apply a workaround by potentially using external SSH configuration options or waiting for an update that includes a configurable timeout feature, as upgrading to a fixed version is not currently an option based on the provided information.