BUG: VSCode IDE Plugin on SSH Connection: "Failed to load tasks."
What version of Codex is running?
0.25.0
Which model were you using?
gpt-5
What platform is your computer?
Darwin 24.6.0 arm64 arm / Linux 6.8.0-78-generic x86_64 x86_64
What steps can reproduce the bug?
When using the Codex IDE plugin (MacOS), either in Cursor or VSCode, and connecting to a remote development server via SSH, the tasks fail to load with message "Failed to load tasks."
What is the expected behavior?
Codex tasks load properly - they do load fine when not connected to a remote server via ssh (when using MacOS and opening a project folder locally). I would expect tasks to load regardless of remote ssh or local project.
Codex CLI 0.25.0 is installed both locally and on the remote linux dev server.
What do you see instead?
"Failed to load tasks."
Additional information
No response
Same issue here, with remote-ssh on Cursor
Same issue on VSCode Insiders for MacOS with Codex 0.5.0
Same issue on VSCode remote-ssh on Ubuntu Linux 22.04 LTS
same issue on cursor and vsocode for macos ubuntu
Also VSCode insiders Windows 11 running in WSL2
0.4.0 also can not running with ssh remote. and it also broke the connection with mac os app!
I have the same issue with it When I connect to a remote server it doesn't load the tasks and I will get this error:
Failed to load tasks.
No matter how much I click on rety It doesn't load the previous history or tasks. Version: 0.4.0
Same issue on local remote WSL too
Same issue on WSL.
Same issue on VSCode Insiders for windows 11 pro
Same issue here with VSCode 1.103.2 for Windows, Codex 0.4.0 plugin and remote-ssh on Ubuntu Linux 24.04.3 LTS
Same issue here in dev container
Same issue on VSCode remote-ssh
Hmm, two things to check:
- Is there a seemingly valid
~/.codex/auth.jsonon the remote host (I assume there is, or chat conversations would not work?) - Is there any sort of firewall or other network configuration that would prevent those requests from going through?
In the settings.json for VS Code, I believe you can set:
"chatgpt.logLevel": "trace", // any of "trace" | "debug" | "info" | "warning" | "error"
and then see log messages from the Codex dropdown in the Output pane (cmd+j to open on macOS, at least).
Is there anything there that sheds light on the error?
@bolinfest - Yes there's a valid ~/.codex/auth.json on both my local macOS system and the remote dev server [Ubuntu 24.04.3 LTS (GNU/Linux 6.8.0-79-generic x86_64)] - codex cli works from both systems using the local auth.json created through the codex cli OAuth login workflow.
I added the suggested settings.json entry and then cmd+j and bring up the output log and see this scrolling constantly, I hadn't checked this before so it may have been throwing these error outputs before even modifying settings.json.
This is the output console while connected via ssh to the remote ubuntu server via ssh.
@ben-vargas Thanks: this is very useful! @gpeal hopefully this gives you something to work with?
If I hit the "Retry" button I see this added line to the thrown error output; this error output logs while connected to the remote SSH server regardless of settings.json addition of chatgpt.logLevel.
Switched to pre-release Codex extension on vscode and it worked
@bytecod3r - I tested on 0.5.3 and not resolved for me personally. Is that the pre-release you're running?
@ben-vargas just in case 0.5.3 is the fix: did you update the extension on the remote host, not just in the client?
And yes (at least for now), we're going with odd minor version number -> pre-release; even minor version number -> mainline release.
@bolinfest - Correct, that's with 0.5.3 pre-release installed both locally on macOS and remote host.
how does one install the latest 0.5.3 version in Cursor? I only see 0.4.0 to install there https://open-vsx.org/extension/openai/chatgpt
@epicwhale unfortunately, Open VSX (which is what Cursor must use because it is not allowed to talk directly to the VS Code Marketplace) does not support pre-releases as the Marketplace does. Currently, we only publish "mainline" releases to Open VSX.
@ben-vargas just in case 0.5.3 is the fix: did you update the extension on the remote host, not just in the client?以防万一 0.5.3 是修复程序:您是否更新了远程主机上的扩展,而不仅仅是在客户端?
And yes (at least for now), we're going with odd minor version number -> pre-release; even minor version number -> mainline release.是的(至少目前),我们将使用奇数次要版本号 -> 预发布;偶数次要版本号 -> 主线发布。
I have updated to the pre-release version 0.5.3, but the issue still exists and has not been resolved. @bolinfest @bytecod3r
@epicwhale - You can try installing VSCode and accessing the pre-release VSIX there by right clicking the listing and downloading appropriate version and then installing that in Cursor. Kind of similar to the "copy all VSCode extensions" that Cursor does when a VSCode user first installs Cursor - that might get around the valid limitation bolinfest mentioned about Open VSX.
@ben-vargas you aren't alone with issue on 0.5.3, seems it's still broken
Failed to load tasks is still an issue on 0.5.3 on ssh connection, both Cursor and VSC Insiders. Running MacOS -> Ubuntu 24.04.
Could you try following the headless authentication docs here?
I was just able to use codex (local and cloud) ssh'd into a remote machine.
@gpeal - What parts specifically from that guide? What do you mean by "I was just able to use codex"?
My remote dev server is already authenticated, the codex cli runs fine there, and even the Codex extension works in terms of sending a message with Chat or Agent mode while connected to the ssh server - this bug/issue is specifically that the task history fails to load. No tasks are shown (for example those run in codex web (https://chatgpt.com/codex) when connected to remote ssh host.
For example, failure to load any cloud tasks in codex extension while ssh'd into remote machine in cursor or vscode:
@gpeal - Also, while connected to the ssh remote host in vscode, if you do cmd+j (toggle the panel), go to output, select Codex filter, do you not have the constant scrolling of errors being thrown as pictured in the images shared above?
@ben-vargas I do not, everything (including cloud) loaded just fine for me. Can you walk me through how you set up your vs code ssh workspace, how you installed the extension, and how you did the headless login?