Mobile Remote only displays direct chats and omits active SSH-backed projects from the paired Windows Codex app

Start by reproducing the paired Windows Remote flow described in the issue, comparing direct/local chats with projects associated with connected SSH hosts. Trace how the mobile interface enumerates projects and chats from the paired desktop app; done means active SSH-backed projects and their existing conversations appear and can be opened from Android.

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

26.730.61639

What subscription do you have?

Pro

What platform is your computer?

Windows for the App, Ubuntu 24.04 and Ubuntu 26.04 for CLI

What issue are you seeing?

Description

I use the Codex desktop app on Windows with multiple SSH connections to Linux systems running Codex CLI. These SSH connections are configured directly inside the Windows Codex app under:

Settings → Connections → SSH

All configured SSH connections show Connected, and I have several active SSH-backed projects that I regularly open and use from the Windows Codex app without any problems.

However, when I connect to that same Windows computer using Remote in the Android mobile app, only direct/local chats appear. None of the active projects associated with the Windows app’s SSH connections are displayed.

These are not arbitrary SSH sessions launched manually in PowerShell. They are established SSH connections recognized by the Codex desktop app, and the projects are already visible and functional in the desktop app.

Environment
Host: Codex desktop app on Windows
Client: ChatGPT/Codex app on Android
Both devices signed into the same account
Control this PC enabled on Windows
Mobile device successfully paired with the Windows computer
Multiple SSH connections configured in the Windows Codex app
All SSH connections show Connected
Multiple active SSH-backed projects are visible and usable in the desktop app

Impact

This prevents me from monitoring or continuing my active Linux development projects from mobile, even though:

The Windows computer is online and paired successfully.
The SSH connections are active.
The projects work normally in the Windows desktop app.
Direct chats from that same Windows host appear correctly on mobile.

The current behavior makes Remote useful only for direct Windows chats and breaks continuity for users whose primary Codex workflow uses the desktop app’s SSH connections.

What steps can reproduce the bug?

Steps to reproduce

Open the Codex desktop app on Windows.
Go to Settings → Connections → SSH.
Confirm that the configured Linux SSH hosts show Connected.
Open and use one or more projects associated with those SSH connections.
Enable Control this PC and pair the Android mobile app with the Windows computer.
Open Remote on the Android device.
Select the paired Windows computer.
Review the available chats and projects.

What is the expected behavior?

Actual result

Only direct/local Codex chats from the Windows computer are displayed.

The active projects associated with the Windows app’s connected SSH environments do not appear in the mobile Remote interface.

Expected result

The mobile Remote interface should display the active SSH-backed projects and chats that are already recognized, connected, and usable through the paired Windows Codex desktop app.

At minimum, the mobile app should allow existing SSH-backed project conversations to be opened and monitored in the same way as direct/local Codex chats.

Additional information

Additional clarification

This report is not asking the mobile app to discover arbitrary standalone Codex CLI sessions.

The missing projects are already listed as active projects inside the Windows Codex desktop app and are associated with SSH connections that the app reports as connected.

Screenshots

I can provide two screenshots:

Connections screen: Shows multiple SSH connections with a Connected status.
Projects screen: Shows multiple active projects assigned to those SSH hosts.

The individual project and server names have been redacted for privacy.