How ccpm has grown, release by release. Each chapter below is one minor series, with the themed changes and patch fixes that shipped under it. For every tagged build, see GitHub Releases.
Profile backup & cloning, shell completions, prompt and status-line integration, and concurrency-safe credential handling.
Improved
Status line now matches /usage and is colour-coded
·The `5h`/`7d` usage segments now show the percentage **used**, matching Claude's own `/usage` panel, so the numbers line up instead of reading as the inverse.
·The line is now colour-coded: the usage percentage shades green → amber → red as your remaining headroom shrinks, with orange window labels and a yellow reset clock. Set `NO_COLOR` for plain text.
Added
In-TUI status line: see which profile is running, plus usage and limits
·`ccpm run` now shows which profile a session is using right inside the Claude Code window — a status line pinned to the bottom that reads e.g. `⬢ work · Sonnet 4.6 · ctx 34% · 5h 58% ↺16:15 · 7d 88% · $1.23`.
·For Claude Pro/Max accounts it surfaces how much of your rolling **5-hour and 7-day usage windows** is left (remaining %, with the reset time), plus current context fill and session cost. API-key profiles show profile, model, and cost.
·It's wired in automatically when a profile has no status line of its own, and never overwrites one you set in `~/.claude/settings.json`, a profile, or a trusted project. Opt out with `ccpm config set statusline false`, per-launch with `ccpm run <profile> --no-statusline`, or remove an injected one with `ccpm settings statusline "" --profile <name>`.
v0.5.0
Added
Profile backup, cloning, shell completions, and prompt integration
·`ccpm export <profile>` packages a profile's skills, agents, commands, rules, hooks, MCP servers, plugins, and settings into a portable `.tar.gz`. `ccpm import-bundle <file>` restores it on another machine (path-traversal-safe). Credentials are excluded by default — re-authenticate with `ccpm auth refresh` after restoring, or pass `--include-credentials` for a trusted same-user move.
·`ccpm clone <source> <new-name>` duplicates an existing profile (assets, settings, and auth). Pass `--no-auth` for an assets-only copy. Note: OAuth clones share the source account's tokens, so for a long-lived clone prefer `--no-auth` and a fresh login.
·`ccpm completion bash|zsh|fish|powershell` emits shell completion scripts, including live completion of your profile names for `run`, `use`, `remove`, `rename`, `set-default`, `clone`, and `export`.
·`ccpm prompt` prints the active profile name for embedding in your shell prompt (PS1, starship, powerlevel10k), so a terminal always shows which account it's bound to. Supports `--format` and `--show-default`.
·`ccpm list --json` emits machine-readable JSON for scripting, CI, and status lines.
·`ccpm doctor --fix` prunes dangling shared-asset symlinks (doctor was previously read-only).
·Distribution: the macOS/Linux/Windows builds now ship with cosign-signed checksums.
FixedSecurity
Concurrency-safe credential handling and hardening
·Credential- and config-mutating commands (`set-default`, `rename`, `remove`, `add`, `clone`) now take a global advisory lock, so running two ccpm commands at once can no longer interleave a stale read with a fresh write and clobber a valid refresh token (a cause of spurious `401` re-logins).
·`config.json`, the shared-asset manifest, and the trust list are now written through the crash-safe atomic-write path, eliminating a window where a crash or concurrent write could corrupt them.
·Profile/vault directories and ccpm-created `~/.claude` directories are now created `0700` (owner-only), so credential files aren't enumerable by other local users on a shared host.
·`ccpm rename` reordered its keychain migration and plugin-metadata rewrite so a mid-rename failure can't leave plugin metadata pointing at a directory that was rolled back.
·Fixed a crash where a malformed or truncated stored API key could panic `ccpm status` / `list` / `auth status`; keys are now masked safely and validated on entry.
·The npm installer now verifies the downloaded binary's SHA-256 against the release checksums and pins the download to the installed package version (no more silently fetching `latest`).
v0.4.x
Default-profile UX across IDEs, OAuth correctness on macOS, host-asset cascade, and atomic writes.
ImprovedFixed
`ccpm set-default` now applies to Cursor, VSCode, and Antigravity (macOS)
·`ccpm set-default <profile>` now registers the chosen profile system-wide on macOS via a user-level LaunchAgent and `launchctl setenv CLAUDE_CONFIG_DIR`. Every newly-launched claude process (terminal, Cursor, VSCode, Antigravity, any GUI app) inherits the profile automatically. Restart any open IDE windows once to pick up the change; future launches and future logins are automatic.
·`ccpm unset-default` removes the LaunchAgent and unsets the env.
·Works around a Claude Code v2.1.x bug where the startup OAuth refresh path misfires when CLAUDE_CONFIG_DIR resolves to bare `~/.claude` even with valid tokens in the keychain.
·Linux and Windows: keychain and identity sync work as before; the GUI-wide env mechanism is macOS-only for now. Terminal use on those platforms is already covered by `ccpm shell-init`.
ImprovedFixed
`ccpm shell-init` now wraps `claude` for terminal use
·`ccpm shell-init` now emits a `claude()` shell function alongside `ccpm()`. When `CLAUDE_CONFIG_DIR` is unset, plain `claude` invocations from your terminal transparently route through whichever profile `ccpm set-default` selected. This sidesteps a Claude Code v2.1.138 startup-refresh path that 401s when `CLAUDE_CONFIG_DIR` resolves to the bare `~/.claude` even with valid OAuth tokens in the keychain.
·Added `ccpm config get default_dir`. Prints the default profile's absolute path, or empty if no default is set. Used by the `claude()` wrapper; useful for scripts that need the same lookup.
·After upgrading, open a fresh terminal (or `source ~/.zshrc`) to pick up the new wrapper. IDE extensions launch claude directly and are not covered by the wrapper.
Fixed
`set-default` no longer reintroduces stale OAuth tokens
·`ccpm set-default` now folds the current default-slot OAuth payload (and identity in `~/.claude.json`) back into the previously-default profile before loading the new selection. Without this, plain `claude` / VSCode invocations would silently rotate the refresh token in the default slot only, and a later `set-default` of the same profile could copy a stale, already-rotated refresh token back into the default slot, causing the next `claude` call to fail with `401 Invalid authentication credentials`.
·Save-back is best-effort: any failure prints a yellow warning and the new default still applies.
FixedImproved
Profile rename and default IDE account
·`ccpm rename` rewrites absolute profile paths inside plugin metadata so renamed profiles keep plugins and skills resolving.
·`ccpm set-default` for OAuth profiles syncs cached identity fields into `~/.claude.json` so the CLI welcome banner matches the selected default profile.
Added
Consolidate and audit tooling
·`ccpm consolidate` audits drift across host, share, and profile scopes with safe auto-fixes for dangling symlinks and stale plugin caches; a bundled slash skill documents deeper cleanup.
FixedImproved
OAuth on macOS after renames and status accuracy
·`ccpm rename` migrates namespaced macOS keychain OAuth entries when a profile directory moves.
·`ccpm list` and auth status treat short-lived access tokens paired with a refresh token as healthy instead of warning on hourly expiry.
·macOS keychain writes for OAuth use the Security CLI so stored payloads match what Claude Code reads (no go-keyring base64 wrapper).
Improved
Windows OAuth path (experimental)
·Experimental Windows credential-manager path for OAuth, mirroring the macOS namespacing model. Still needs real-host verification.
ImprovedSecurity
Atomic writes and managed plugins
·Multi-file updates (settings + `.claude.json`, manifest + symlinks) go through transactional atomic writes.
·First-class `ccpm plugin` marketplace install, per-profile enable/disable, and garbage collection of shared cache.
AddedImproved
Host asset cascade
·Skills, agents, commands, rules, hooks, and host plugin trees under `~/.claude/` can auto-adopt into profiles (opt-out via config or `--no-auto-adopt`).
·`ccpm doctor` reports cascade and shadowed names where profile-local assets win.
v0.3.x
Parity with native Claude Code: scoped MCP, transports, permissions, sessions, and a simpler settings model.
AddedImproved
Parity with native Claude Code CLI
·`ccpm run` forwards unknown flags to `claude` without a `--` separator; `--ccpm-env` for one-shot env overrides.
·MCP: scopes (global / profile / project), HTTP and SSE transports, `ccpm mcp auth` via native Claude in profile scope.
·`ccpm env`, `ccpm permissions`, `ccpm sessions list`, managed-settings merge layer, and project settings/MCP discovery from CWD.
ImprovedFixed
Settings model simplification
·Removed the ccpm-managed global settings fragment. Cross-profile baseline is `~/.claude/settings.json`, with per-profile fragments and owned-keys for durable overrides.
FixedImproved
MCP materialization and imports
·MCP servers materialize into `<profile>/.claude.json` (where Claude Code reads them), not `settings.json`.
·`MaterializeMCP` merges host `~/.claude.json` user-scope MCPs so installs outside ccpm still appear in profiles.
·`ccpm import default` can import MCP entries from `~/.claude.json` with per-item selection.
v0.2.x
Release automation and cross-platform path handling.
AddedImproved
Release automation and quality
·`scripts/release.sh` automates version bump, checks, tag, GitHub Release, and npm publish with optional `--stash` for partial trees.
·Import and fingerprint paths handle symlinked directories and Windows test sandboxes (`USERPROFILE`) correctly.
v0.1.x
The first public ccpm: profile isolation via `CLAUDE_CONFIG_DIR`, OAuth + API key auth, encrypted vault, shared assets, and a Go-built single binary on npm, curl, and go install.
·Per-profile isolation by setting `CLAUDE_CONFIG_DIR` to `~/.ccpm/profiles/<name>/`. Two terminals, two accounts, zero conflicts.
·OAuth and API key flows. API keys live in the OS keychain (macOS Keychain, Linux Secret Service, Windows Credential Manager).
·Encrypted credential vault under `~/.ccpm/vault/` using AES-256-GCM with a master key in the OS keychain.
·Shared asset store at `~/.ccpm/share/` for skills and other assets, symlinked into profiles to avoid duplication.
·Distribution: single static Go binary published to npm (`@ngcodes/ccpm`), curl installer, and `go install`. CI via GitHub Actions; release packaging via GoReleaser.
Have a question about a change? Open the docs and use Ask Me (⌘K / Ctrl+K).