How to Run Multiple Claude Code Instances

If you use two or more Claude accounts for Claude Code, for example a personal one and a work one, it is possible to run both at the same time, with optionally different configurations or the same configurations.

Running a Second Instance

On Linux and Mac, the default Claude Code settings directory is located in your home directory at ~/.claude. It is possible to specify an alternative directory for the settings.

For example, to create a second directory for use with Claude Code, run:

mkdir ~/.claude-secondary

Then launch Claude Code specifying the directory:

CLAUDE_CONFIG_DIR=~/.claude-secondary claude

The first Claude account can be run as normal with:

claude

Creating Shell Aliases

You can also create aliases in Bash or ZSH, so running cc in your terminal will open your default instance, and cc2 will open the secondary.

Add the following to your ~/.bashrc or ~/.zshrc file:

# Launch Claude Code default (personal) account
alias cc='claude'

# Launch Claude Code secondary account
alias cc2='CLAUDE_CONFIG_DIR=~/.claude-secondary claude'

After adding these aliases, reload your shell configuration by running source ~/.bashrc or source ~/.zshrc. Then you can launch your default Claude Code instance with just cc and your secondary instance with cc2.

Alternative Alias Names

# Work and personal accounts
alias claude-work='CLAUDE_CONFIG_DIR=~/.claude-work claude'
alias claude-personal='claude'

# Client-specific instances
alias claude-client-a='CLAUDE_CONFIG_DIR=~/.claude-client-a claude'
alias claude-client-b='CLAUDE_CONFIG_DIR=~/.claude-client-b claude'

Synchronising Configuration Files

You can also create symbolic links (symlinks) to keep one configuration across both instances. For example, to share the Skills directory from the primary instance to the secondary:

ln -s ~/.claude/skills ~/.claude-secondary/skills

Other Configuration Files You Can Share

# Share keybindings
ln -s ~/.claude/keybindings.json ~/.claude-secondary/keybindings.json

# Share MCP servers configuration
ln -s ~/.claude/mcp_servers.json ~/.claude-secondary/mcp_servers.json

# Share global settings (use with caution - authentication tokens are stored here)
ln -s ~/.claude/settings.json ~/.claude-secondary/settings.json

Important: Be cautious when sharing settings.json as it contains authentication tokens. Sharing this file between instances means both instances will use the same Claude account.

Frequently Asked Questions

Do I need multiple Claude subscriptions to run multiple instances?

Not necessarily. You can run multiple instances with the same account by sharing the settings.json file between configuration directories. However, the more common use case is to use separate Claude accounts for different purposes, such as a personal account and a work account.

Will my conversations be shared between instances?

No. Each instance maintains its own conversation history and context within its respective configuration directory. The conversations are stored locally and are separate for each instance.

Can I run more than two instances?

Yes, you can run as many instances as you need. Simply create additional configuration directories and use the CLAUDE_CONFIG_DIR environment variable to specify which configuration to use. For example, you could have ~/.claude-work, ~/.claude-personal, ~/.claude-client-a, etc.

Do multiple instances count as separate usage?

Yes, if each instance is using a different Claude account. Each account has its own usage limits and token consumption. If multiple instances share the same account, they all count towards the same account's usage limits.

What happens if I delete a secondary configuration directory?

Deleting a secondary configuration directory will remove all settings, conversation history, and authentication tokens specific to that instance. If you've created symlinks to share configuration files from your primary instance, the original files in ~/.claude will remain unaffected.