claude-multiprofile
Enables teams to maintain strict separation between personal, work, and client contexts without context leakage or credential conflicts—reducing compliance r…
Run multiple Claude Desktop and Claude Code accounts side by side on macOS. Fully isolated profiles for personal, work, and clients.
- Run separate Claude instances for client work without exposing personal conversation history
- Maintain isolated API keys and chat histories across professional and personal projects simultaneously
- Switch between work and client profiles on macOS without logging in and out repeatedly
Enables teams to maintain strict separation between personal, work, and client contexts without context leakage or credential conflicts—reducing compliance risk and improving security posture for consultants managing multiple client engagements.
Consultants and contractors managing multiple client projects requiring isolated Claude instances on macOS.
https://github.com/jmdarre-v/claude-multiprofile
By jmdarre-v
How to Get It
claude plugins install jmdarre-v/claude-multiprofile
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me run separate Claude instances for client work without exposing personal conversation history
Trust Signals Auto-scanned
Community Pulse New
- Claude-multiprofile: run multiple Claude accounts side by side on macOS — Hacker News · 3 pts
1 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 48 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 48 GitHub stars; contributors unknown; last commit 0d ago; license MIT.