Feature Request: SSH Environment Support for Remote Development Workspaces

Resolved 💬 2 comments Opened Feb 15, 2026 by aneym Closed Feb 15, 2026

Summary

Requesting SSH environment support to allow the Codex app (running locally) to connect to and work on remote development servers via SSH. This would enable developers to leverage powerful remote dev environments while keeping the Codex app experience local, with the ability to share chats across environments.

Use Case

As a developer who:

  • Runs the Codex app on a personal laptop (macOS)
  • Has development environments on remote servers (cloud VMs, on-premise servers, etc.)
  • Wants to use Codex to work on code that lives on those remote servers

Currently, there's no way to point Codex at an SSH-accessible remote workspace. This limits Codex's utility for teams that use remote development environments.

Proposed Solution

Add SSH remote workspace support similar to VS Code's Remote-SSH extension:

  1. SSH Configuration: Allow users to configure SSH connections (host, user, key/auth method)
  2. Remote File System: Access and edit files on the remote server through Codex's UI
  3. Remote Execution: Run commands, builds, and tests on the remote environment
  4. Chat Synchronization: Ability to share or access chat sessions across local and remote contexts
  5. Workspace Persistence: Remember remote workspace state between sessions

Benefits

  • Hardware flexibility: Use a lightweight laptop to control powerful remote dev machines
  • Environment consistency: Work in consistent, pre-configured remote environments
  • Security: Keep source code and secrets on secured remote infrastructure
  • Collaboration: Share development environments and chat context with teammates
  • Mobility: Seamlessly switch between local and remote work without losing context

Additional Context

This feature would make Codex competitive with other AI coding assistants that offer remote development capabilities, and would be especially valuable for:

  • Enterprise teams with strict security requirements (code stays on-premise)
  • Developers using cloud-based development environments (GitHub Codespaces alternatives)
  • Users with limited local compute resources who rely on remote machines

---

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗