Codex Desktop Windows SSH mobile availability fails with false expired session error

What version of the Codex App are you using?

Codex Desktop for Windows with Codex CLI 0.143.0.

The SSH remote host also has Codex CLI 0.143.0 available from a login shell.

What platform is your computer?

Controller host:

Windows / x86_64
Codex Desktop using a WSL-backed runtime/engine

Remote host:

Linux / x86_64 over SSH

Mobile:

ChatGPT iOS app

What issue are you seeing?

Codex mobile remote control works for the Windows Codex Desktop host, but enabling mobile/signed-in-device access for an SSH connection fails with an incorrect session-expired error.

The SSH connection itself appears healthy:

• The SSH remote is configured in Codex Desktop under Settings > Connections > SSH.
• The SSH entry shows a green/connected status indicator.
• The Desktop app can use the SSH connection.
• The remote login shell can find codex, and codex --version reports 0.143.0.
• ChatGPT iOS has been paired with Codex Desktop successfully.
• Remote Control for the Windows Desktop host is enabled and works from the iPhone.

However, when trying to allow mobile/signed-in devices for the SSH connection, Codex Desktop shows this error:

Your Codex session on this device has expired. Sign in again and try again.

Signing out and signing back in to Codex Desktop does not fix it. The normal Codex Desktop session is clearly still valid: the Desktop app is signed in, chat works, and the iPhone pairing / Desktop remote control continues to work.

This makes the error look specific to the SSH remote-control availability path rather than a general expired login session.

Steps to reproduce

1. On Windows, sign in to Codex Desktop.
2. Pair ChatGPT iOS with Codex Desktop using the Codex mobile setup flow.
3. Enable Remote Control / signed-in device access for the Windows Desktop host.
4. Confirm the iPhone can control the Windows Desktop host.
5. Add or discover an SSH host in Codex Desktop.
6. Confirm the SSH host is reachable and appears connected/green in Settings > Connections > SSH.
7. Click the mobile/signed-in-devices control for the SSH connection.
8. Confirm the prompt to allow devices to control this SSH connection.

Observed:

Your Codex session on this device has expired. Sign in again and try again.

Expected:

The SSH connection should become available from signed-in/mobile devices, or the UI should show a specific actionable error if the SSH remote cannot be exposed.

Diagnostics already checked

• Re-authenticating Codex Desktop did not resolve the SSH enablement error.
• Re-pairing ChatGPT iOS with Codex Desktop succeeded and did not resolve the SSH enablement error.
• The desktop remote-control feature flag is enabled locally.
• The remote-control enrollment table for the Desktop host was checked while debugging the mobile pairing path.
• The SSH remote itself is reachable and healthy from the Desktop side.
• The failure is isolated to enabling mobile/signed-in-device access for the SSH connection.

Related issues checked

I searched existing openai/codex issues before filing. The closest issues I found are related, but none appear to describe this exact Windows Desktop + SSH availability toggle + false session-expired error:

• #23699: SSH remote-control toggle/restart behavior with mobile, but the reported failure mode is different and macOS-based.
• #23527: Mobile does not show SSH remote projects from a connected desktop host, but that is a project visibility issue after setup, not a failure to enable SSH availability.
• #23466: Feature request/bug around inheriting desktop SSH hosts on mobile, related conceptually but not this session-expired error.
• #23112: Stale local mobile pairing state can break Codex mobile setup, but in this case mobile pairing and Desktop remote control work.
• #23915 and #22804: Remote-control authorization/account-id mismatch issues, related auth area but not this SSH availability toggle error.
• #25080: Mobile cannot connect to a Linux SSH remote project on some Codex versions, but this issue fails earlier while enabling SSH access from signed-in devices.

I also searched for the exact text:

Your Codex session on this device has expired

and did not find an existing exact match.

Why this looks like a bug

The UI says the Codex session expired, but the same Desktop app session remains valid for normal Codex use and for mobile Remote Control of the Desktop host. The error appears to be thrown only by the SSH signed-in-device availability path.

The product should either reuse the valid Desktop/session state for this SSH availability action or surface the real underlying authorization/state error.