Skip to content

VS Code Remote-SSH: Codex extension stuck on “Thinking”; only works with "openai.chatgpt": ["ui"] but then can’t read remote files (paths show C:/...) #2987

@MstarLioning

Description

@MstarLioning

What version of the VS Code extension are you using?

0.4.0

Which IDE are you using?

VS Code

What platform is your computer?

ssh Linux and local windows

What steps can reproduce the bug?

Hi everyone—looking for help! I’m using VS Code to connect to a remote server over SSH. I also set up reverse port forwarding to my local proxy so the remote terminal can access the internet. From the terminal on the server, both Claude Code and Codex work fine.

However, after installing the Codex extension in VS Code, no matter what I type it just stays on “Thinking” and eventually throws:

error sending request for url (https://chatgpt.com/backend-api/codex/responses)

ChatGPT suggested adding this to settings.json:

"remote.extensionKind": { "openai.chatgpt": ["ui"] }

If I do that, the Codex panel can produce responses, but it can’t read any files on the server—every path is shown as C:/xxx, as if the extension is running locally instead of on the remote host.

How can I fix this so the extension works and can access files on the remote server? Any advice would be greatly appreciated!

What is the expected behavior?

No response

What do you see instead?

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    extensionIssues related to the VS Code extensionremote-workspaceIssues relating to non-local filesystems/ssh/devcontainers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions