›_ Codex Issues
Codex Issues / #29335

Codex App Settings > Connections fails to discover Remote SSH hosts

Open 💬 0 comments Opened Jun 21, 2026 by jo-pillar

What version of the Codex App are you using (From “About Codex” dialog)?

Codex App 26.616.51431 (4212)

What subscription do you have?

codex pro 100

What platform is your computer?

Darwin 25.2.0 arm64 arm

What issue are you seeing?

When I open Codex App and go to Settings -> Connections to use Remote SSH, Codex fails during the SSH host discovery step.

The UI reports:

Failed to discover remote SSH connections.

My ~/.ssh/config contains concrete Host entries, and normal SSH from the terminal can use these aliases. The failure does not appear to be specific to ProxyJump; it can still happen with SSH config entries that do not use ProxyJump.

A sanitized shape-only check of the SSH config is:

1: Host ali-pc00
2: HostName
3: User
4: ProxyJump
5: Host ali-pc10
6: HostName
7: User
8: Port

The important point is that the config contains normal concrete host aliases. Codex App fails before I can select or use the Remote SSH connection.

<img width="1754" height="810" alt="Image" src="https://github.com/user-attachments/assets/9f2d44c4-c3e8-4450-9cee-1e3fcb23a89c" />

What steps can reproduce the bug?

  1. On macOS, create ~/.ssh/config with one or more concrete host aliases.
  2. Confirm the aliases work from a terminal, for example:
ssh <alias>
  1. Open Codex App.
  2. Go to Settings -> Connections.
  3. Try to discover or use Remote SSH connections.
  4. Observe the error:
Failed to discover remote SSH connections.

What is the expected behavior?

Codex App should discover valid SSH host aliases from ~/.ssh/config, or at least show an actionable diagnostic for the specific alias/config option that failed.

Ideally the UI/logs would distinguish between:

  • malformed SSH config
  • unsupported SSH config directive
  • failed alias resolution
  • connection timeout
  • authentication failure
  • no discoverable hosts

Additional information

Related issues found while searching, but not exact duplicates:

  • #13693 contains similar SSH discovery log text, but the reported issue is Windows/WSL app startup behavior.
  • #18819 discusses SSH connect timeout configuration.
  • #23102 discusses SSH/jump-host behavior for a different route.

This report is specifically about Codex Desktop on macOS failing during Remote SSH discovery from ~/.ssh/config

View original on GitHub ↗