Codex IDE extension fails to load in VS Code Remote-SSH, while Codex CLI works correctly

Open 💬 11 comments Opened Jun 11, 2026 by lucastdeoliveira1-bit
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

26.602.71036

What subscription do you have?

ChatGPT Plus

Which IDE are you using?

VS Code

What platform is your computer?

Linux 6.17.0-22-generic x86_64 x86_64

What issue are you seeing?

Hello,

I am experiencing a problem with the Codex IDE extension in Visual Studio Code when using Remote-SSH. I connect to a remote Linux server through VS Code and open my remote workspace there. The Codex CLI works correctly in the remote terminal: I can log in with my ChatGPT account, check the login status, and run simple Codex commands successfully. However, the Codex IDE extension inside VS Code does not load properly. The sidebar/chat interface either stays blank or does not open as expected.

I have already tried reinstalling the Codex extension, clearing Codex configuration files, resetting the remote VS Code server, clearing local VS Code caches, reconnecting through Remote-SSH, and logging in again. The Codex CLI continues to work correctly, but the VS Code Codex IDE extension still fails to load. Because of this, it seems that the issue may be related to the Codex IDE extension, VS Code Remote-SSH, the VS Code extension host, or a compatibility issue with the current VS Code/Node.js environment.

Could someone from the support or engineering team help me understand what is causing this problem and how to fix it? I would like to use Codex directly inside the VS Code IDE with access to my remote workspace, but currently only the terminal version works.

<img width="1921" height="1047" alt="Image" src="https://github.com/user-attachments/assets/d46f367d-e58b-4c4c-8122-6f932f541526" />

What steps can reproduce the bug?

Steps to reproduce:

  1. Open Visual Studio Code on a local Ubuntu Linux machine.
  1. Connect to a remote Linux server using VS Code Remote-SSH.

Example with PII redacted:

``bash
ssh -p 22 <user>@<remote-host>
``

  1. Open a remote workspace folder in VS Code.

Example:

``text
/data/users/<user>
``

  1. Install the OpenAI Codex / ChatGPT extension in the remote SSH environment, so that it is enabled on the remote host.

Installed remote extension

  1. In the remote VS Code terminal, verify that the Codex CLI works:

```bash
cd /data/users/<user>

codex --version
codex login status
codex exec -s read-only --skip-git-repo-check "Responda exatamente: ok"
```

Expected CLI output:

``text
codex-cli 0.137.0-alpha.4
Logged in using ChatGPT
ok
``

  1. Try to open the Codex IDE sidebar/chat in VS Code using the Codex icon or the command palette.

Example:

``text
Codex: Open Sidebar
``

  1. The Codex sidebar does not load correctly. It either remains blank or does not open as expected.

What is the expected behavior?

The Codex IDE sidebar should open normally in VS Code when connected through Remote-SSH.

Since the Codex CLI works correctly in the same remote workspace and is already logged in, I expected the VS Code Codex extension to also load correctly and allow me to use Codex inside the IDE with access to the remote files.

Additional information

_No response_

View original on GitHub ↗

11 Comments

github-actions[bot] contributor · 1 month ago

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

  • #26951

Powered by Codex Action

YLMiami · 9 days ago

Did you find a durable fix?

hungtrieu07 · 7 days ago
Did you find a durable fix?

I am still experiencing this issue.

Velythyl · 7 days ago

I also am struggling with this issue; the Codex tab or standalone VSCode-integrated window do not work at all for me.

YLMiami · 7 days ago
I also am struggling with this issue; the Codex tab or standalone VSCode-integrated window do not work at all for me.

It's kind of ridiculous that OpenAI's product has this issue. I'm just gonna use Codex CLI until then I guess...

Adefioye · 3 days ago

I am currently experiencing same issue on a runpod remote machine.

Adefioye · 3 days ago

It's been roughly over a month since this issue has been reported with no fix yet. pretty sad.

YLMiami · 3 days ago
It's been roughly over a month since this issue has been reported with no fix yet. pretty sad.

Very very strange to me why this would be unfixed for this long... All the fixes I've seen had to do with people aewkwardly deleting logs... I just dont' want to deal with that. Thinking about cancelling over this.

YOU HEAR THAT SAM!? CANCELLING!!!!

radeksulc · 1 day ago

Content of the Codex windows works on local Windows 11. But once connected to a remote environment using ssh, the Codex window remains blank. Just re-tested. A fundamental limitation blocking me from getting Codex subscription. VSCode remote ssh is a typical setup which works with Claude Code without any issues. Needs to be fixed urgently.

hungtrieu07 · 1 day ago

Today, I can use Codex in IDE extension on VS Code Remote-SSH, you guys can check there is any extension update.

<img width="503" height="1079" alt="Image" src="https://github.com/user-attachments/assets/263e942d-f879-403a-a423-7df967cf7a4d" />

YLMiami · 12 hours ago
Today, I can use Codex in IDE extension on VS Code Remote-SSH, you guys can check there is any extension update. <img alt="Image" width="503" height="1079" src="https://private-user-images.githubusercontent.com/69461968/623712464-263e942d-f879-403a-a423-7df967cf7a4d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODQ1NjMwMjAsIm5iZiI6MTc4NDU2MjcyMCwicGF0aCI6Ii82OTQ2MTk2OC82MjM3MTI0NjQtMjYzZTk0MmQtZjg3OS00MDNhLWE0MjMtN2RmOTY3Y2Y3YTRkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA3MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNzIwVDE1NTIwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI3NjEyMWQ4NGUxZTY1N2E4MWNmMWZiYTBkOTIyYWM3NTBkNDMxYWM2YmY1MWE3ZmIxYWM2NzE3MjYwMDU5ZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.o1UDztYyCDI7hi0J4W6ISTnpF6a_24WZnSo9YV-Dfs8">

Worked for me, and then didn't work for me again.