Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Support SSH remote development in Codex Desktop App [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18114•Fetched 2026-04-17 08:32:39
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
JianbinLiu-CFLabJianbinLiu-CFLab
Participants
github-actions[bot]github-actions[bot]JianbinLiu-CFLabJianbinLiu-CFLab
Timeline (top)
labeled ×2closed ×1commented ×1

Fix Action

Fix / Workaround

Many development workflows rely on centralized dev servers, on-premise GPU clusters, or cloud VMs. Currently, using Codex in these environments forces users to choose between suboptimal workarounds:

  • Installing the Codex CLI on the server (works for terminal users but lacks GUI file browsing/diff views).
  • Using VS Code with the Codex extension via Remote-SSH (works well, but some users prefer the dedicated, streamlined interface of the Desktop App).
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

App

What feature would you like to see?

Currently, the Codex Desktop App only supports opening and working with local projects on the same machine where the app is installed. For developers who primarily work on remote servers, virtual machines, or cloud development environments accessed via SSH, the Desktop App is effectively unusable for real coding tasks.

I would like to see native SSH remote project support added to the Codex Desktop App, similar to the experience provided by the VS Code Remote - SSH extension.

Desired Behavior

  1. Connect to a remote host: The ability to input an SSH connection string (e.g., user@host:port) and provide authentication (password, key file, or agent forwarding).
  2. Browse remote filesystem: The Codex file tree should display the directory structure of the remote server.
  3. Execute Codex in the remote context: Codex's AI model should have direct access to the remote files and the remote terminal environment. This ensures that file edits, shell commands, and context gathering happen exactly where the code lives.
  4. Transparent terminal integration: The built-in terminal should open a shell session on the remote server automatically.

Use Case & Motivation

Many development workflows rely on centralized dev servers, on-premise GPU clusters, or cloud VMs. Currently, using Codex in these environments forces users to choose between suboptimal workarounds:

  • Installing the Codex CLI on the server (works for terminal users but lacks GUI file browsing/diff views).
  • Using VS Code with the Codex extension via Remote-SSH (works well, but some users prefer the dedicated, streamlined interface of the Desktop App).

Adding SSH support to the Desktop App would unify the experience and make Codex a first-class citizen for remote development, regardless of the user's preferred IDE.

Potential Implementation Notes

The VS Code Remote Development extensions provide a proven reference architecture for this feature:

  1. Establish an SSH connection and install a small "Codex Server" daemon on the remote host.
  2. The local Desktop App acts as a thin UI client.
  3. All language analysis and file operations occur on the remote host.

Thank you for considering this request. It would significantly expand the utility of the Desktop App for enterprise and infrastructure-focused developers.

Additional information

No response

extent analysis

TL;DR

To add native SSH remote project support to the Codex Desktop App, consider implementing a client-server architecture similar to the VS Code Remote - SSH extension.

Guidance

  • Study the VS Code Remote Development extensions as a reference architecture for implementing SSH support in the Codex Desktop App.
  • Establishing an SSH connection and installing a small "Codex Server" daemon on the remote host could be a viable approach.
  • Design the local Desktop App to act as a thin UI client, with all language analysis and file operations occurring on the remote host.
  • Consider the security implications of authentication and authorization for remote connections.

Example

No code snippet is provided as the issue focuses on a high-level feature request rather than a specific coding problem.

Notes

The implementation details may vary depending on the specific requirements and constraints of the Codex Desktop App and its underlying technology stack.

Recommendation

Apply a workaround by using the VS Code Remote - SSH extension with the Codex extension, as this provides a similar experience to the requested feature, although it may not be the exact same as having native support in the Codex Desktop App.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#GPU setup#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING