{"slug": "access-codex-from-another-machine-remote-ssh-or-migration", "title": "Access Codex from another machine: Remote, SSH, or migration?", "summary": "A developer built Codex Migrate, an MIT-licensed tool that transfers local Codex state between Macs over SSH, staging and validating incoming data and verifying a destination rollback backup before replacement while preserving the new machine's existing Codex login and installation identity. The project distinguishes one-time migration from Codex Remote, Remote SSH, and true synchronization, warning that blindly copying all of ~/.codex can duplicate machine-specific authentication, runtime locks, and caches. A signed and Apple-notarized Apple-silicon beta is sold for $50 once, and the developer notes the independent project is not affiliated with or endorsed by OpenAI.", "body_md": "\"Use Codex from another machine\" sounds like one problem. It is actually four different workflows, and choosing the wrong one can create duplicated state or a broken destination.\n\nUse **Codex Remote** when Codex should keep running on the original computer and you want to supervise it from another authorized device. The host must remain awake, online, and running Codex.\n\nOpenAI's current documentation: [Remote connections](https://developers.openai.com/codex/remote-connections) and [Work with Codex from anywhere](https://openai.com/index/work-with-codex-from-anywhere/).\n\nUse **Remote SSH** when your laptop should operate against a project and execution environment that remain on a different Mac. The remote Mac still owns the files, tools, and runtime.\n\nThis is remote access, not a copy and not synchronization.\n\nThis is a **migration**. Signing into the same ChatGPT account does not turn all local Codex state and workspace files into ordinary cloud history.\n\nA complete move may need to preserve:\n\n`.git`, branches, worktrees, stashes, uncommitted files, and untracked files;\nAvoid blindly copying all of `~/.codex`. Authentication, installation identity, runtime locks, caches, and other machine-specific data should not be cloned onto the destination.\n\nI built [Codex Migrate](https://migrate.segeren.com/) for this Mac-to-Mac case. It inventories the selected scope, transfers directly over SSH, stages and validates the incoming data, verifies a destination rollback backup before replacement, and preserves the new Mac's existing Codex login and installation identity.\n\nThe [CLI and source](https://github.com/jsegeren/codex-migrate) are MIT licensed. The signed and Apple-notarized Apple-silicon beta is $50 once, with best-effort support and a 30-day refund policy.\n\nThat is **synchronization**, not migration. It requires conflict handling for Git state, uncommitted files, sessions, paths, and machine-local configuration. Repeatedly mirroring all of `~/.codex` is not a safe substitute.\n\n| What you want | Use | \n|---|---|\n| Check the running host from your phone | Codex Remote | \n| Keep the project on another computer | Remote SSH | \n| Retire the old Mac and continue on the new one | One-time migration | \n| Work on the same state from two active computers | A real synchronization system | \n\nI wrote a longer, source-linked comparison here: [Access Codex from another machine](https://migrate.segeren.com/access-codex-from-another-machine).\n\nDisclosure: I maintain Codex Migrate. It is an independent project and is not affiliated with or endorsed by OpenAI.", "url": "https://wpnews.pro/news/access-codex-from-another-machine-remote-ssh-or-migration", "canonical_source": "https://dev.to/jsegeren/access-codex-from-another-machine-remote-ssh-or-migration-56mc", "published_at": "2026-09-11 01:00:46+00:00", "updated_at": "2026-09-11 01:52:37.878732+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents"], "entities": ["Codex Migrate", "OpenAI", "Codex", "Codex Remote", "Remote SSH", "ChatGPT", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/access-codex-from-another-machine-remote-ssh-or-migration", "markdown": "https://wpnews.pro/news/access-codex-from-another-machine-remote-ssh-or-migration.md", "text": "https://wpnews.pro/news/access-codex-from-another-machine-remote-ssh-or-migration.txt", "jsonld": "https://wpnews.pro/news/access-codex-from-another-machine-remote-ssh-or-migration.jsonld"}}