Use a remote SSH project in the ChatGPT or Codex desktop app Print

  • codex, remote project, ssh host
  • 0

Quick answer

A remote project runs commands and edits files on the SSH host. It is different from running a local coding agent that occasionally deploys over SSH. The remote workflow needs Codex installed and authenticated on that host, so first confirm that the account is suitable for a development agent.

Choose local, remote, or cloud deliberately

A local project, a remote SSH host, and a published cloud environment have different files and permissions. A cloud environment does not automatically inherit laptop sign-ins, running services, or hosting credentials. Use a local project and selective deployment when a hosted account is unsuitable for a long-running development agent.

Reference: current Codex environments.

Before you start

Check the current official remote-connection documentation and your app version. Your local computer needs a tested SSH alias. The remote account needs a supported shell, executable storage, sufficient resources, network access, and a Codex command available in its login environment.

What to do

  1. Ask the hosting provider whether the specific shared account can run a remote coding agent. Do not infer suitability merely from an SSH icon.
  2. Add and test a concrete alias in your local SSH configuration. Verify the server identity before accepting its host key.
  3. If the host is suitable, install and authenticate the official remote tooling through its supported flow, without putting tokens into chat or public folders.
  4. Add the SSH host in the desktop app's connection settings, choose a dedicated project folder, and retain per-task permissions for publishing.

Check the result

Confirm the displayed run location, remote folder, and Git state. Make a harmless development change and verify that it appears only in the intended environment.

If something does not work

If the account cannot run the app server, use a local project plus controlled SSH/SFTP deployment. Never expose a Codex app-server listener directly to the public internet to bypass SSH setup.

Related help

Official references

Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.

AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.


Was this answer helpful?

« Back