claude-account-sync 0.5.1 → 0.5.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -58,6 +58,8 @@ clp mcp add shadcn --all --command npx --args "shadcn@latest,mcp"
|
|
|
58
58
|
clp mcp sync --from oauth --to office,z # make profiles match
|
|
59
59
|
```
|
|
60
60
|
|
|
61
|
+
> **Scope:** `clp` manages **user-scope** MCP servers only (the top-level `mcpServers` in `~/.claude.json`). Local/project-scoped servers — added with `claude mcp add` at its default scope, stored under `projects[...]` or in a project `.mcp.json` — are intentionally left untouched (they're tied to a working directory). If a server isn't showing up in `clp mcp list`, re-add it at user scope: `claude mcp add <name> --scope user -- <command>`, then `clp adopt --yes`.
|
|
62
|
+
|
|
61
63
|
### New profile for a new account
|
|
62
64
|
|
|
63
65
|
```bash
|
|
@@ -107,6 +109,27 @@ anything Claude Code supports works — the form just gives the common keys frie
|
|
|
107
109
|
labels and a preset for the base URL. It travels with sync and bundles like everything
|
|
108
110
|
else, token included (via the encrypted secrets channel).
|
|
109
111
|
|
|
112
|
+
### Where secrets are stored (per-OS setup)
|
|
113
|
+
|
|
114
|
+
`clp` keeps API tokens out of your rc/config files by putting them in the OS credential store, picked automatically:
|
|
115
|
+
|
|
116
|
+
| OS | Backend | Setup |
|
|
117
|
+
|---|---|---|
|
|
118
|
+
| macOS | Keychain | automatic |
|
|
119
|
+
| Windows | DPAPI (via PowerShell) | automatic |
|
|
120
|
+
| **Linux desktop** | `secret-tool` (libsecret) | `sudo apt install libsecret-tools` (or `dnf install libsecret`) — needs a running keyring daemon (GNOME Keyring / KWallet) |
|
|
121
|
+
| **Linux headless / server** | AES‑256‑GCM encrypted file | set a passphrase (below) — servers have no keyring daemon, so libsecret isn't an option |
|
|
122
|
+
|
|
123
|
+
**Headless Linux / server (no desktop keyring):** the encrypted-file backend needs a passphrase in the environment. `clp` (and `clp ui`) read it at launch:
|
|
124
|
+
|
|
125
|
+
```bash
|
|
126
|
+
# add to ~/.bashrc so it persists, then: source ~/.bashrc
|
|
127
|
+
export CCPROFILES_PASSPHRASE='a-long-passphrase-you-will-remember'
|
|
128
|
+
clp ui
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
Secrets then encrypt to `~/.ccprofiles/secrets.enc`. **The passphrase is the decryption key** — keep it safe and unchanged, or the stored secrets become unreadable. (Prefer a systemd `EnvironmentFile` or your secrets manager over `.bashrc` if the box is shared.) Without a keyring *and* without this passphrase, the Secrets tab and `clp secrets …` will report the backend is unavailable.
|
|
132
|
+
|
|
110
133
|
### Replicate to a second machine
|
|
111
134
|
|
|
112
135
|
```bash
|
|
@@ -178,7 +201,7 @@ All mutating commands support `--dry-run`. Every mutation backs up the files it
|
|
|
178
201
|
| `error: no manifest yet` | Run `clp adopt --yes` first — it builds the manifest from your existing profiles |
|
|
179
202
|
| `zsh: command not found: clp` | Not linked/installed — see Install; if just linked, run `rehash` |
|
|
180
203
|
| ``cannot reach <host> — is `ccprofiles serve` running?`` | Start `clp serve` on the other device; check you're on the same network and the port matches |
|
|
181
|
-
| `encrypted-file backend requires a passphrase` |
|
|
204
|
+
| `encrypted-file backend requires a passphrase` / secrets tab errors | No OS keyring available. **Linux desktop:** `sudo apt install libsecret-tools` + a running keyring. **Headless Linux / server:** `export CCPROFILES_PASSPHRASE='…'` before `clp ui` (persist in `~/.bashrc`). **Windows:** secrets use DPAPI automatically (needs PowerShell). See [Where secrets are stored](#where-secrets-are-stored-per-os-setup) |
|
|
182
205
|
| `cl-*` launcher not found on Windows | Use PowerShell 7 (`pwsh`), not Windows PowerShell 5.1; reload with `. $PROFILE`; if scripts are blocked run `Set-ExecutionPolicy -Scope CurrentUser RemoteSigned`. Confirm `$PROFILE` matches `Documents\PowerShell\Microsoft.PowerShell_profile.ps1` (OneDrive can redirect it) |
|
|
183
206
|
| Profile shows account `-` after sync | Expected — run `/login` inside that profile once; OAuth sessions don't sync |
|
|
184
207
|
| Something went wrong after `apply` | Restore from `~/.ccprofiles/backups/<latest>/` |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-account-sync",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.3",
|
|
4
4
|
"description": "Manage multiple Claude Code accounts/profiles — MCP drift sync, keychain secrets, and encrypted LAN replication between machines. CLI: ccprofiles (alias clp).",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|