+ New profile asks for:
work. It defines the folder ~/.claude-work and the command claude-work.CLAUDE.md, skills, plugins, agents, MCP servers and per-project settings from an existing profile. Optionally it also copies conversations, history and project memories. General memories (your home project) are always copied.CLAUDE.md, permissions, skills, agents, commands, output styles and MCP servers, as the profile’s own copies. Nothing is shared and no conversation comes along.What a new profile never gets:
.credentials.json) and account data (oauthAccount, userID): run the new command and use /login. A copied token could be invalidated when the original profile refreshes it.cc-profiles also creates the launcher ~/.local/bin/claude-<id> (see Getting started) and adds the /cc-profiles command to the new profile, so you can open this app from it right away. If the profile shares commands with the source profile, the command goes into the source and reaches both through the link. A cc-profiles.md that cc-profiles did not write is left as it is.
Items you choose to share that the source profile does not have yet are created there, empty, so the link always works.
A template is a reusable starting point for new profiles. Templates… in the Profiles tab lists them and saves a new one from any profile.
A template holds the profile’s settings.json and settings.local.json (with permissions and hooks), CLAUDE.md, skills/, agents/, commands/, output-styles/ and the MCP servers of .claude.json (user scope). It never holds conversations, prompt history, memories, plugins, login credentials (.credentials.json) or account data (oauthAccount, userID). Shared items are saved as real files, so the template does not depend on the source profile.
Templates are .zip files in ~/.cc-profiles/templates/, in the same format as an export without conversations. Creating a profile from a template uses the import code, so paths inside settings.local.json point to the new folder.
Saving, deleting and creating a profile from a template each have a backup. A deleted template goes to the backup and Restore brings it back.
Edit changes:
claude and cannot change. A command that already exists as another program is refused.The folder never changes: the profile’s files store absolute paths to it, so renaming it would break them.
Delete offers two options:
In both cases the profile leaves config.json and its launcher (or shell alias) is removed. Type the profile’s name to enable the button.
The dialog shows what the chosen option does before you confirm: how many projects, conversations, memories and prompts move and where, and under Show the files and folders it touches every item, including the launcher, the alias line in your shell file, the entry in config.json and the folder that goes to the backup. The preview changes nothing.
Deleting is refused:
claude process is running in the profile, or one of its conversations was written in the last 2 minutes), because a running Claude Code would keep writing into a folder that is gone.Under Sharing, each secondary profile has a switch per item:
| Item | What sharing means |
|---|---|
skills |
same local skills everywhere |
plugins |
same installed plugin files (enabling is per profile, in settings.json) |
agents |
same custom subagents |
commands |
same custom slash commands |
CLAUDE.md |
same global instructions |
settings.json |
same settings, status line, enabled plugins, permissions and hooks |
Turning a switch on replaces the profile’s own copy with a link. The old copy goes to the backup, and the confirmation lists anything the source profile does not have, so you can copy it over first. Turning it off gives the profile an independent copy of the current source content.
Both confirmations have Show the files and folders it touches: the own copy that goes to the backup, each item only that copy has, the link and its target, and what is created in the source profile when it does not have the item yet; when separating, the link that goes to the backup and the files copied in its place.