Regression: project-sorted view no longer shows SSH host alias for remote projects

Resolved 💬 2 comments Opened Jun 10, 2026 by Saafo Closed Jun 17, 2026

What version of Codex are you using?

Codex App 26.608.12217

What issue are you seeing?

After updating to Codex App 26.608.12217, the project-sorted view no longer shows the SSH host name / SSH alias associated with remote projects.

I use multiple SSH Remote Connections. Some remote hosts contain projects with identical or very similar repository names and directory structures. In the project-sorted view, the UI now only shows the project name/path without the SSH host identity, so multiple remote projects can look identical and it becomes unclear which SSH host each project belongs to.

I also checked Settings and could not find any option to enable or restore SSH host name display.

What steps can reproduce the bug?

  1. Configure multiple SSH hosts in Codex App Remote Connections.
  2. Add remote projects from different SSH hosts.
  3. Use projects that have identical or similar names/paths across those SSH hosts.
  4. Switch the sidebar/project list to project-sorted mode.
  5. Observe that the SSH host name/alias is not displayed for the remote projects.

What is the expected behavior?

The project list should clearly indicate which SSH host a remote project belongs to.

Possible UI options:

  • Display the SSH alias next to the project name.
  • Display the SSH host name as a badge/tag.
  • Show the project as something like ssh-prod:/workspace/my-repo or display ssh-prod / ssh-staging under otherwise identical project names.

What is the actual behavior?

Projects from different SSH hosts appear visually indistinguishable in the project-sorted view. When multiple SSH connections are configured, it is not possible to tell which remote host a Project belongs to from the project list alone.

Additional information

This appears to be a regression after updating to Codex App 26.608.12217. It is especially problematic for users managing multiple remote environments such as production, staging, development, and personal servers through SSH Remote Connections.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗