Account groups (scopes) are named, poolable seat sets for Work, Job A, or Client B — not a flat dump of every login into one rotator. Name a group, put only those seats in it, pool within the set, activate with pc scope use, and isolate Claude Code memory when isolation is on.
Account groups (scopes) partition linked Claude accounts so you can name any group, group any linked accounts, keep context isolated per group, and select an active group for what you are working as right now.
Quick path: pc scope create Work → pc scope create Personal → drag (or pc scope add) each login → pc scope use <id> when you switch roles. Isolation defaults on.
What this is
- Name any group (Work, Personal, Client-Acme, Project-X) — free-form labels.
- Group any linked accounts into that set (drag or CLI).
- Keep context and memory isolated per group when isolation is on.
- Select an active group for what you are working as right now.
- Manage membership in the dashboard or CLI (
pc scope).
Credentials remain private per account. Groups never share OAuth. State: ~/.power-claude/state/account-scopes.json (mode 0600).
Quick start (dashboard)
- Open Power Claude → Your Profiles.
- Under Account groups, click + New group (e.g.
Work). Isolation defaults on. - Create
Personalthe same way. - Drag accounts from Ungrouped onto the correct group.
- Click Use this group.
- Switch groups when your role changes (or clear active group).
CLI
pc scope create Work
pc scope create Personal
pc scope list
pc scope add <work-id> This email address is being protected from spambots. You need JavaScript enabled to view it.
pc scope add <personal-id> This email address is being protected from spambots. You need JavaScript enabled to view it.
pc scope use <work-id>
pc scope use none
pc scope isolation <id> isolated
pc scope move This email address is being protected from spambots. You need JavaScript enabled to view it. <personal-id>
pc scope delete <id>
Aliases: scopes, group, groups.
Concepts
| Term | Meaning |
|---|---|
| Group / scope | Named set of accounts |
| Active group | Selected group for current work |
| Isolated | Per-group claude-shared/scopes/<id>/projects/ tree |
| Global | Shared machine-wide projects tree |
| Ungrouped | Accounts in no group |
Name groups like personas
| Name | Purpose |
|---|---|
| Work | Company seats only |
| Personal | Home / learning seats |
| Client-* | One isolated group per client |
| Project-* | Billing or delivery boundary |
| Sandbox | Experimental agents |
Create with + New group or pc scope create <Name>, then drag any accounts onto the card.
Common setups
- Work + personal: two isolated groups; activate when switching roles.
- Agency / clients: one isolated group per client; activate before that monorepo.
- Product team seats: one product group with all allowed seats; personal elsewhere.
- Project billing boundaries: one group per project/invoice line (local organization — not Anthropic billing).
CLI reference
| Command | Action |
|---|---|
pc scope list | List groups, members, active * |
pc scope create <label> | Create isolated group |
pc scope create <label> --global | Create with shared context |
pc scope use <id|none> | Set/clear active group + apply layout |
pc scope add <id> <account> | Move account into group |
pc scope move <account> <id|none> | Move or ungroup |
pc scope isolation <id> isolated|global | Toggle isolation |
pc scope delete <id> | Delete group (accounts ungrouped) |
FAQ
Does this bypass rate limits? No.
Share logins between accounts? No.
One account in two groups? No — single membership. Use tags for multi-label.
Deletes sessions? No.
Group any accounts and name them freely? Yes.