Skip to main content

​
Concurrent Sessions

Run multiple Claude CLI instances simultaneously. Different account profiles normally use different Claude config directories, while launching the same profile twice reuses the same directory and shared state.

​
Overview

​
Architecture

CCS uses CLAUDE_CONFIG_DIR to select the Claude config directory for each account profile:
When you run ccs work "task":
  1. Sets CLAUDE_CONFIG_DIR=~/.ccs/instances/work/
  2. Claude loads credentials from that directory
  3. That session reuses the work profile’s state directory
That gives you a simple rule of thumb:
  • Different profiles such as work and personal normally use different directories
  • The same profile such as work + work reuses one directory
  • If you configure continuity inheritance, different profile names can intentionally reuse the same directory too

​
Instance Structure

Each account profile gets its own default directory:

​
Performance

​
Limitations

Running the same profile in multiple terminals is allowed, but both terminals reuse the same CLAUDE_CONFIG_DIR and shared state. Use different profiles when you want stronger separation.
This is not a special CCS-only restriction. Any two launches that point at the same Claude config directory share mutable state.

​
Other Limitations

  • CLAUDE_CONFIG_DIR is undocumented (keep Claude CLI updated)
  • Same-profile launches share history, todos, logs, and other mutable artifacts
  • Non-bare profiles share commands, skills, agents, plugins, settings.json, and CLAUDE.md via ~/.ccs/shared/
  • Sessions/logs accumulate (manual cleanup if needed)
For account and native session recovery, see Resume the Correct Session Lane.

​
Shared Resources

By default, non-bare account profiles reuse the shared CCS layout for commands, skills, agents, plugins, settings.json, and user CLAUDE.md.
If you created a profile with --bare, it opts out of that shared layout on purpose.

​
Cleanup