Claude Profiles
Per-project account bindings that control which configuration directory each project's coding sessions use.
Claude Profiles let you bind different Anthropic accounts and configurations to different projects. Each profile points to a separate ~/.claude (or ~/.claude-<name>) config directory, controlling which account, session history, and CLI settings a project's sessions use.
Why use profiles?
- Multiple accounts — switch between personal and work Anthropic accounts per project.
- Isolated configuration — different projects can have different settings, allowed tools, and session histories.
- Team workflows — use a shared team account for one project and your personal account for another.
Setting a profile
- Right-click a project in the sidebar.
- Select Change Claude Profile...
- Pick from detected profiles, or create a new one.
Scape scans for profiles by looking at ~/.claude* directories on your system.
How it works
When Scape launches a session for a project, it injects the profile path as the CLAUDE_CONFIG_DIR environment variable. This determines:
- Anthropic account — OAuth credentials for the API.
- Session history — past conversations and context.
- CLI configuration — settings, allowed tools, and MCP server registrations.
Scope
- Profiles are stored on the project level — each project can use a different profile.
- Worktrees inherit the parent project's profile via canonical repo root resolution.
- Changing the profile on a project applies to all repos in that project.