fxClaudeRaycast extension and CLI · Free

Every Claude account,
one keystroke away.

Give personal and work accounts their own Claude workspace, each signed in and side by side. Open or focus the right one from Raycast or the terminal. Free and open source, from the makers of fxCodex.

curl -fsSL https://capturecontext.dev/tools/fxclaude/install.sh | sh

macOS 14+ · Downloads and verifies the signed GitHub release

primary

Back at it, Max

work

Good morning, Max

Not a screenshotPick a workspace to bring its Claude window forward. Use ↑↓ and ↵, ⌘K for actions, or ⌥F to bring fxClaude back.

A workspace for each account.
No signing out, no copying state around.

fxclaudeWorkspaces
  • primaryYour existing Claude setup~/Library/…/ClaudeRunning
  • workyou@company.com…/workspaces/workRunning
  • personalyou@home.net…/workspaces/personalStopped

Separate local profiles

Each workspace keeps its own chats, projects, connectors and sign-in. Your current setup stays as the primary workspace.

Return to the right window

fxClaude remembers each running instance and brings it forward instead of launching a second copy.

Made for scripts

Add --json, or set FXCLAUDE_JSON=1, for a versioned envelope that scripts and launchers can rely on.

The same workspaces in the terminal

Create, open, focus and check workspaces from the shell. The Raycast extension runs the same commands.

From Raycast in three keys.
The extension for every day, the CLI for everything else.

  1. 01

    Open fxClaude

    Run the fxClaude command in Raycast. primary is the Claude setup you already have.

  2. 02

    Create a workspace

    Name it work or personal, then sign in once in its own Claude window.

  3. 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 starts with its own CLAUDE_USER_DATA_DIR, Electron --user-data-dir and CLAUDE_CONFIG_DIR, so chats, projects, Claude Code settings and sign-ins stay apart.

The window that is already open

fxClaude 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 Claude. fxClaude never asks for credentials or API keys.

And the small things you would miss.

  • Raycast extension
  • Every action is a command
  • --json with a versioned envelope
  • status --all
  • workspace paths
  • use sets the default
  • Erase or delete a workspace
  • Integration attributes for launchers
  • open-url for sign-in links
  • Claude Code per workspace
  • Universal binary
  • Signed and notarized
  • MIT licensed

FAQ

Can I keep two Claude accounts open at once?

Yes. Each workspace is its own Claude 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 Claude setup?

Nothing. It becomes the primary workspace and keeps using Claude's usual data. Managed workspaces live next to it.

Do I need Raycast?

fxClaude 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 fxClaude in it, the right Claude is a keystroke away.

Does it work with Claude Code?

Yes. Each workspace gets its own Claude Code config, shared by the app's Code tab and fxclaude cli in the terminal, so settings, history and memory stay per account. Run /login once in fxclaude cli for each workspace.

Can a sign-in link land in the right workspace?

Yes. fxclaude open-url work hands a claude:// link to that workspace's Claude only, instead of whichever one macOS picks. Arx can run it for you, with a different workspace for each profile.

Is there one for Codex?

Yes. fxCodex came first: the same workspaces, Raycast extension and CLI for the Codex app, plus optional app renaming.

Where do my sign-ins live?

Inside each workspace's own Claude data. fxClaude never sees credentials or API keys. It only keeps workspace names, paths and the process it launched.

Could a Claude update break it?

It relies on how the desktop app separates its user data, which could change. fxClaude is checked against current Claude releases, and each release will say which versions it supports.

How do I install and update it?

With the install script above or a signed, notarized release from GitHub. There is no self-updater yet, so run the script again to update. Requires macOS 14 or later.

How do I clean up?

fxclaude erase resets a workspace and fxclaude delete removes it. Both ask first, and the primary workspace is never touched.

Open the right Claude.
Every time, in a few keystrokes.

Using Codex too? Try fxCodex.