remote connection displays gpt5.5 as custom model

Resolved 💬 7 comments Opened Apr 23, 2026 by winoros Closed May 19, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.422.20832 (2025)

What subscription do you have?

Pro

What platform is your computer?

Darwin 24.2.0 arm64 arm

What issue are you seeing?

<img width="2106" height="1214" alt="Image" src="https://github.com/user-attachments/assets/ae22a3b3-6b88-4486-a11a-87e4e7ba6a3f" />

As you can see, the codex cli in the remote machine is 5.5+high.
But when I switch to the app and use remote connection, the displayed model is custom and I can not choose 5.5 from the menu.

<img width="798" height="526" alt="Image" src="https://github.com/user-attachments/assets/75bf508d-3489-4cc4-bff4-c4e03468c763" />

What steps can reproduce the bug?

Remote machine's codex cli is 0.124 and choose gpt5.5. Then go to app and open a remote project.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19200
  • #19192
  • #17933

Powered by Codex Action

lpjiang97 · 2 months ago

Same issue here.

winoros · 2 months ago

The problem still exists. I can only use the cli to use 5.5 now.

mrkn-xica · 2 months ago

I’m seeing the same issue on the remote host, where Codex v0.124.0 is installed.

Interestingly, I can use GPT-5.5 when connecting to localhost.

<img width="438" height="336" alt="Image" src="https://github.com/user-attachments/assets/9129f44b-e66c-494a-aef0-5966f8f741da" />

<img width="408" height="357" alt="Image" src="https://github.com/user-attachments/assets/7fa487e4-c656-45b5-bc5e-8c135742f6cf" />

winoros · 2 months ago

According to the findings from https://github.com/openai/codex/issues/19300, rebooting my server solved the problem.

DanishjeetSingh · 2 months ago

i ran into the same issue just now and resetting the codex app-server is a much better alternative than rebooting the full server.

winoros · 2 months ago

I see that there's an option to restart the remote codex app server now.
Mark the issue as closed.