codex - 💡(How to fix) Fix Codex App Remote SSH uses id_rsa by default even if it doesn't exist [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18301Fetched 2026-04-18 05:56:31
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2commented ×1

Code Example

$ ls ~/.ssh
authorized_keys config          id_ed25519      id_ed25519.pub  known_hosts     known_hosts.old
RAW_BUFFERClick to expand / collapse

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

26.415.21839 (1763)

What subscription do you have?

ChatGPT Enterprise

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Under codex->settings->connections->SSH connections,

discovered connections as well as added connections with no identity file specified will use id_rsa as default identity, even when it doesn't exist.

What steps can reproduce the bug?

  1. Use ssh-keygen in ~/.ssh to have id_ed25519 key without id_rsa like below (backup id_rsa)
$ ls ~/.ssh
authorized_keys config          id_ed25519      id_ed25519.pub  known_hosts     known_hosts.old
  1. Add a machine under ~/.ssh/config without the IdentityFile attribute

  2. Open Codex App, you will see Codex try to use id_rsa when it should be using id_ed25519

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The Codex App may need a configuration update to correctly handle SSH connections without an explicitly specified identity file, defaulting to the first available key instead of always assuming id_rsa.

Guidance

  • Verify that the SSH connections in the Codex App are correctly configured to use the intended identity file by checking the ~/.ssh/config file for each connection.
  • Consider specifying the IdentityFile attribute in the ~/.ssh/config file for each connection to ensure the correct key is used.
  • If no IdentityFile is specified, the Codex App should ideally default to the first available key in the ~/.ssh directory, such as id_ed25519 in this case, rather than assuming id_rsa.
  • Review the Codex App documentation to see if there are any settings or configurations that can be adjusted to change the default behavior for SSH connections without an explicitly specified identity file.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The behavior described might be specific to the version of the Codex App being used (26.415.21839) and the platform (Darwin 25.3.0 arm64 arm). It's also possible that this is an intended behavior that can be overridden through configuration settings not immediately apparent from the issue description.

Recommendation

Apply workaround: Specify the IdentityFile attribute in the ~/.ssh/config file for each SSH connection to ensure the correct key is used, as this provides a direct solution to the problem described without relying on potential changes to the Codex App's default behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING