Give personal and work accounts their own Codex workspace, each signed in and side by side. Open or focus the right one from Raycast or the terminal. Free and open source.
curl -fsSL https://capturecontext.dev/tools/fxcodex/install.sh | sh
macOS 14+ · Downloads and verifies the signed GitHub release
CodexFileEditViewWindowHelp
primary
What should we build?
Choose projectThis computer
Do anything
Approve for meGPT-6 Astra High
work
What should we build?
Choose projectThis computer
Do anything
Approve for meGPT-6 Astra High
Workspaces
primaryCurrentRunning
client
workRunning
Management
StatusHealthy
Codex
Preferences
Not a screenshotPick a workspace to bring its Codex window forward. Use ↑↓ and ↵, ⌘K for actions, or ⌥F to bring fxCodex back.
A workspace for each account. No signing out, no copying state around.
fxcodexWorkspaces
primaryYour existing Codex setup~/.codexRunning
workyou@company.com…/workspaces/workRunning
personalyou@home.net…/workspaces/personalStopped
Separate local profiles
Each workspace keeps its own Codex settings, sessions, integrations and app data. Your current setup stays as the primary workspace.
personal
workFocused
Return to the right window
fxCodex remembers each running instance and brings it forward instead of launching a second copy.
ChatGPT.app
Codex.app
fxcodex preferences set auto-rename true
Keep calling Codex, Codex
Opt in and fxCodex restores the Codex name whenever an update installs the app as ChatGPT.app.
zsh
~ % fxcodex workspace create work --use --open✓ Created workspace work✓ Opened Codex with an isolated profile~ % fxcodex exec -- "summarize the open pull requests" CODEX_HOME=~/Library/…/fxcodex/workspaces/work~ % fxcodex status --all primary running pid 4182 work running pid 5530 personal stopped
The same profile in the terminal
Terminal commands point CODEX_HOME at the selected workspace, so scripts and interactive sessions use the same account as its window.
From Raycast in three keys. The extension for every day, the CLI for everything else.
⌘Space01
Open fxCodex
Run the fxCodex command in Raycast. primary is the Codex setup you already have.
⌘N02
Create a workspace
Name it work or personal, then sign in once in its own Codex window.
↵03
Focus or open
Running workspaces come forward. Stopped ones open. Never a duplicate.
Under the hood. Plain directories and a runtime record.
Separate desktop data
Each managed instance gets its own CODEX_HOME, CODEX_ELECTRON_USER_DATA_PATH and Electron --user-data-dir.
The window that is already open
fxCodex records the process, bundle and launch date of each workspace and checks them before it activates a window.
No account switching
Nothing swaps accounts inside Codex. fxCodex never asks for credentials or API keys.
And the small things you would miss.
Raycast extension
Same workspaces in the terminal
--json with a versioned envelope
Self-update, SHA-256 verified
open-url for sign-in links
status --all
workspace paths
Raycast extension
Same workspaces in the terminal
--json with a versioned envelope
Self-update, SHA-256 verified
open-url for sign-in links
status --all
workspace paths
Rename workspaces
Erase or delete a workspace
Homebrew tap
Signed and notarized
Guided uninstall
MIT licensed
Rename workspaces
Erase or delete a workspace
Homebrew tap
Signed and notarized
Guided uninstall
MIT licensed
Honorable dependencies
Built on excellent open-source work
fxCodex uses these libraries for terminal prompts, command parsing, dependencies, and local process control
Yes. Each workspace is its own Codex app instance with its own sign-in, so work and personal windows run side by side. Nothing signs out when you switch.
What happens to my current Codex setup?
Nothing. It becomes the primary workspace and keeps using Codex's usual directories. Managed workspaces live next to it.
Do I need Raycast?
fxCodex works without it: every action is a CLI command, and the extension calls the same CLI. But you need Raycast anyway. It is one of the best things you can install on a Mac, and with fxCodex in it, the right Codex is a keystroke away.
Where do my sign-ins live?
Inside each workspace's own Codex data. fxCodex never sees credentials or API keys. It only keeps workspace names, paths and the process it launched.
Why would Codex.app become ChatGPT.app?
Some app updates install Codex under the ChatGPT.app name. Turn on auto-rename and fxCodex restores Codex.app before its next command. It is off until you opt in.
Can a sign-in link land in the right workspace?
Yes. fxcodex open-url work hands a codex:// link to that workspace's Codex only, instead of whichever one macOS picks. Arx can run it for you, with a different workspace for each profile.
Is there one for Claude?
Yes. fxClaude brings the same workspaces, Raycast extension and CLI to the Claude desktop app, and gives each workspace its own Claude Code config too.
How do I install and update it?
With Homebrew (brew install capturecontext/tap/fxcodex), the install script above or a signed release from GitHub. fxcodex update checks the SHA-256 of every download. Requires macOS 14 or later.
How do I clean up?
fxcodex erase resets a workspace, fxcodex delete removes it, and fxcodex uninstall walks you through removing fxCodex itself.
Open the right Codex. Every time, in a few keystrokes.