mmsge

Agent Profile Manager

Name: Agent Profile Manager
Author: mmsge

Data community

SOURCE https://github.com/mmsge/agent-profile-manager

Description

The Claude Profile Manager is a CLI that wraps the Claude cli and helps you stay compliant with multiple accounts. It re-routes claude commands to the correct profile and accounts, making sure data does not overlap. It helps you create new profiles as well. First version is MacOS only.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Agent Profile Manager

`agent-profile` keeps several AI agent accounts separate on one Mac, and audits that the separation actually holds.

Claude Code has no built-in account switcher. The only mechanism for keeping two accounts apart is giving each its own config root, selected by the `CLAUDE_CONFIG_DIR` environment variable. Doing that by hand works right up until it does not: a copy-paste slip labels one account's sessions as another's, one root gets pinned to the *default* root and quietly overloads it, and the desktop app never gets pinned at all. This tool removes the hand-maintained duplication rather than adding a layer on top of it.

It is named for agents rather than for Claude because the same problem will arrive with ollama, codex and whatever comes next. Claude is the only agent implemented today.

What a profile is

One profile is one account, and it owns two directories:


Config root	`~/.claude-`, the value of `CLAUDE_CONFIG_DIR`
App data dir	`~/Library/Application Support/Claude-`, the value of `--user-data-dir`

The config root holds everything the agent stores: settings, session transcripts, auto memory, commands, skills, agents, plugins, plans, backups, the credential and the state file. Two profiles therefore share no file at all.

Why nothing is shared

**No exceptions.** No symlinks, no shared parent directory, no copying common commands into every root, no seeding a new root from an existing one, no template of default settings. `new` creates an empty root.

The cost is real and worth stating: a fresh root has no settings, no hooks and none of the guardrails your other profiles have. Set those up in the new root directly. Do not copy them across, because a copied file is a file that drifts.

The tool also never touches credentials beyond checking that one exists, never edits the agent's own state files, and never migrates data between roots.