Title: Remote SSH projects fail with token refresh errors after successful authentication (Windows Desktop 26.608.12217)

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

Codex Desktop 26.608.12217

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11

What issue are you seeing?

Title: Remote SSH projects fail with token refresh errors after successful authentication (Windows Desktop 26.608.12217)

Environment:

• Codex Desktop 26.608.12217
• Windows 11
• ChatGPT Plus account
• Remote Linux host: Ubuntu 24.04.4 LTS
• SSH connectivity verified independently

Problem:
Local projects work correctly, but any remote SSH-backed project fails immediately when a prompt is submitted.

Observed errors:

• "Failed to refresh token: 400 Bad Request: Your session has ended. Please log in again."
• "Your access token could not be refreshed because you have since logged out or signed in to another account. Please sign in again."

What was tested:

• Created a brand-new empty repository on the remote host.
• Existing repositories and new repositories both fail.
• SSH access from Windows works normally.
• Codex Web works normally.
• Local Codex projects work normally.
• Logging out and back in does not resolve the issue.
• Resetting local Codex state and authentication files does not resolve the issue.

Additional observation:
The remote connection authentication flow appears to complete successfully, but subsequent prompts still fail with token refresh errors.

Expected behaviour:
After successful authentication and SSH connection, prompts should execute against the remote repository.

Actual behaviour:
Every prompt fails before repository access occurs.

What steps can reproduce the bug?

What was tested:

• Created a brand-new empty repository on the remote host.
• Existing repositories and new repositories both fail.
• SSH access from Windows works normally.
• Codex Web works normally.
• Local Codex projects work normally.
• Logging out and back in does not resolve the issue.
• Resetting local Codex state and authentication files does not resolve the issue.

Additional observation:
The remote connection authentication flow appears to complete successfully, but subsequent prompts still fail with token refresh errors.

Expected behaviour:
After successful authentication and SSH connection, prompts should execute against the remote repository.

Actual behaviour:
Every prompt fails before repository access occurs.

What is the expected behavior?

_No response_

Additional information

_No response_