claude-profiles
Manage multiple Claude Code profiles across machines. Share skills, memories, plugins, and settings while keeping credentials separate.
uvx claude-profiles create r # new profile -> ~/.rclaude
uvx claude-profiles create work --copy-creds-from s # with credentials
uvx claude-profiles init # or discover existing ones
uvx claude-profiles status # check health
Profile names
The claude suffix is implicit — profiles are just the prefix:
| Directory | Profile | Alias |
|---|---|---|
~/.claude |
default (canonical) |
claude |
~/.sclaude |
s |
sclaude |
~/.rclaude |
r |
rclaude |
Launching profiles
uvx claude-profiles run s
uvx claude-profiles run r --model opus
# Or add aliases to your shell rc:
eval "$(uvx claude-profiles shell-init)"
# Now just type:
sclaude
rclaude -p 'explain this'
What's shared vs separate
| Shared (symlinked to ~/.claude) | Per-profile |
|---|---|
skills/ — custom slash commands |
.credentials.json — auth tokens |
projects/ — project memories |
.claude.json — account identity |
plugins/ — installed plugins |
history.jsonl — session history |
plans/ — saved plans |
sessions/, cache/, debug/ |
settings.json — preferences |
Credential sync
Push credentials between local profiles, SSH hosts, and Docker containers.
uvx claude-profiles sync -f local:s -t remote:gpu-box -v
uvx claude-profiles sync -f local:default -t docker:abc123
uvx claude-profiles sync -f remote:serverA -t remote:serverB
Location syntax
local[:profile] Local profile (default src: s, dst: default)
remote:host[:profile] SSH host (default: ~/.claude)
docker:container[:path] Docker container (default: /root/.claude)
Commands
| Command | Description |
|---|---|
create <name> [--copy-creds-from] |
Create a new profile with symlinks |
init |
Discover existing profiles, set up symlinks |
status |
Show profiles, link health, credential status |
run <profile> [args...] |
Launch claude with a profile |
shell-init |
Print shell aliases for .zshrc/.bashrc |
link |
Re-create symlinks if broken |
sync -f SRC -t DST [-v] |
Sync credentials between locations |
Release files for claude-profiles 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| claude_profiles-0.2.1.tar.gz | 9.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| claude_profiles-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.6 kB
Release files / claude_profiles-0.2.1.tar.gz
| Download URL | claude_profiles-0.2.1.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92aeeb892067469f7e3bffd746b0d94d18710db5c4b07265bef73e6d0cd425e3
|
|
BLAKE2b-256 checksum How to use checksums |
24ed73ff724c87d5dde3ad6de104afa129fd54a0ec415b93f8ee6edc165f282b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logRelease files / claude_profiles-0.2.1-py3-none-any.whl
| Download URL | claude_profiles-0.2.1-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79658db5b2fd0838e73fee45e266b1457825074ce4c87295c99234c11b277ad6
|
|
BLAKE2b-256 checksum How to use checksums |
7bafcf9bf8fbcf46569a3a57aa6475d982acb7176e6ac9e37699071f1f24546d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency log