claude-profile 1.0.2__tar.gz

claude_profile-1.0.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 CloudOpsWorld and claude-profile contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

claude_profile-1.0.2/MANIFEST.in

@@ -0,0 +1,2 @@
+include README.md RELEASING.md LICENSE
+include scripts/claudectl_entry.py scripts/demo.ps1

claude_profile-1.0.2/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: claude-profile
+Version: 1.0.2
+Summary: Per-customer profiles for Claude Code and Claude Desktop: separate logins, AI platforms, MCP servers, skills and history, side by side.
+Author: claude-profile contributors
+License: MIT
+Project-URL: Homepage, https://github.com/CloudOpsWorld/claude-profile
+Project-URL: Repository, https://github.com/CloudOpsWorld/claude-profile
+Project-URL: Issues, https://github.com/CloudOpsWorld/claude-profile/issues
+Keywords: claude,claude-code,claude-desktop,anthropic,profiles,mcp,deepseek,openrouter,cli
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=9.1.1; extra == "dev"
+Requires-Dist: ruff>=0.15.21; extra == "dev"
+Requires-Dist: mypy>=2.3.0; extra == "dev"
+Requires-Dist: build>=1.5.1; extra == "dev"
+Dynamic: license-file
+
+# claudectl
+
+Use Claude Code with a separate profile for each customer, on Windows, macOS and Linux. Each profile has its own:
+
+- sign-in or API key
+- AI platform
+- MCP servers
+- skills and plugins
+- session history and memory
+
+Customers can run side by side in separate terminals. Switching never touches a session that's already running, and one customer's Jira or Confluence server never shows up in another customer's session.
+
+claudectl doesn't change anything machine-wide. Your normal `claude` and `~/.claude` keep working exactly as before, and appear as the `default` profile.
+
+It's pure Python 3.10+ with no dependencies beyond the standard library.
+
+## Install
+
+From PyPI (the package is `claude-profile`, the command is `claudectl`):
+
+```bash
+pipx install claude-profile      # or: uv tool install claude-profile   or: pip install claude-profile
+claudectl install               # optional: adds the "Claude Profiles" Start menu picker on Windows
+```
+
+**Without Python:** download a standalone binary from [Releases](https://github.com/CloudOpsWorld/claude-profile/releases) and run it once with `install`, which puts it in `~/.local/bin`:
+- `claudectl-windows-amd64.exe`
+- `claudectl-macos-arm64`
+- `claudectl-linux-amd64`
+
+Each release has `SHA256SUMS` and build provenance you can check with `gh attestation verify <file> --repo CloudOpsWorld/claude-profile`.
+
+**From source:**
+
+```bash
+python claudectl/cli.py install
+```
+
+This copies the single file to `~/.claudectl/app` and puts a launcher in `~/.local/bin`.
+
+To remove claudectl, run `claudectl uninstall` (or `pipx uninstall claude-profile`). Your profiles are kept.
+
+## Daily use
+
+```bash
+claudectl add acme                 # guided: name, AI platform, key or sign-in, bind this folder
+cd ~/work/acme-repo
+claudectl                          # starts Claude Code as ACME, because the folder is bound
+claudectl tab globex               # new terminal tab locked to Globex
+claudectl acme --resume            # any claude arguments pass through
+claudectl mcp add jira -- npx -y <jira-mcp>   # goes into this folder's profile only
+claudectl list                     # profiles, bound folders, active profile, Desktop profile
+```
+
+- **Bound folders** pick the profile automatically. If you start a different profile inside a bound folder, claudectl asks before continuing.
+- **Everywhere else**, `claudectl` uses the active profile. Set it with `claudectl use <name>`.
+- **Every session shows its customer** in Claude Code's status line and in the tab title.
+- **On Windows**, tabs open in Windows Terminal with the customer's color. macOS uses Terminal.app. Linux uses the first terminal it finds: GNOME Terminal, Konsole, kitty, WezTerm, Alacritty or Xfce Terminal.
+
+## Import your existing setup
+
+```bash
+claudectl import --scan     # just show what's in your current Claude setup
+claudectl import            # guided: sort project folders into customer profiles
+```
+
+**What the scan finds:**
+- every project folder Claude has history for (worktrees are folded into their repo)
+- MCP servers, both user-wide and per-project
+- skills, agents, commands and output styles
+- your `CLAUDE.md`, plugins and preferences
+- Claude Desktop's MCP servers
+- leftovers from older switcher scripts: extra `~/.claude-*` config folders, system-wide `ANTHROPIC_*` variables, and lines in your PowerShell or shell profile
+
+It skips temporary folders, folders that no longer exist, your home folder and drive roots.
+
+**The guided import** suggests customers from your folder layout. `D:\work\acme\api` and `D:\work\acme\web` become one `acme` profile, tied to `D:\work\acme`. You can:
+- press Enter to accept each suggestion
+- type a name to rename it or merge it into another profile
+- press `k` to keep those folders in your default setup
+
+Then you pick:
+- the AI platform for each new profile
+- which profiles get which MCP servers
+- whether new profiles get your skills, `CLAUDE.md`, preferences and plugins (plugins are reinstalled cleanly in each profile)
+
+**It only copies.** Each project's history, memory, prompt history, trust settings and per-project MCP servers go into its profile. Your current setup isn't changed, so it's safe while Claude is running.
+
+**Your own sign-in, account details and caches are never copied into a customer profile.** The one exception: a `~/.claude-*` folder left by an older switcher is adopted whole, including its sign-in, because that sign-in belongs to the customer.
+
+You can also work from a file, which is handy for many folders or for repeating the import:
+
+```bash
+claudectl import --plan plan.json                  # write the suggestions to a file you can edit
+claudectl import --apply plan.json --dry-run       # show what would happen
+claudectl import --apply plan.json                 # copy
+claudectl import --apply plan.json --move          # copy, then take it out of the default setup
+```
+
+Running `--apply` again is safe: it never overwrites anything and doesn't duplicate history.
+
+**`--move`** removes the imported customer folders, history and MCP servers from your default setup:
+- It refuses while any Claude Code session is running, including Desktop's Code tab.
+- It backs up your config first.
+- It puts everything it removes in `~/.claudectl/import-backups/`.
+- Desktop's Code tab uses your default setup, so moved history no longer shows up there.
+
+`--from DIR` imports from another Claude config folder instead of `~/.claude`.
+
+## AI platforms
+
+| Platform | How it connects |
+|---|---|
+| Claude subscription: Pro, Max, Team, Enterprise | Browser sign-in on first start. You can lock it to the customer's org UUID. |
+| Anthropic API key | Pay per use. |
+| DeepSeek | Native Claude-compatible endpoint. |
+| OpenRouter | GPT, Gemini and others. Use this for OpenAI customers, with BYOK for their own OpenAI key. |
+| Any Claude-compatible URL | For example a LiteLLM proxy in front of a direct OpenAI key, Moonshot, Z.ai or a company gateway. |
+| AWS Bedrock, Google Vertex | Claude through the customer's own cloud account. |
+
+To add a platform, create `~/.claudectl/providers.json`: a JSON list of entries in the same shape as `BUILTIN_PROVIDERS` at the top of [claudectl/cli.py](claudectl/cli.py). An entry with an existing `id` replaces the built-in one. To change a profile's models, run `claudectl edit <name>`.
+
+**Where API keys are stored:**
+- **Windows:** encrypted with DPAPI, so only your Windows user can read them.
+- **macOS:** in your login Keychain.
+- **Linux:** in your keyring through `secret-tool`. Without a keyring, in a file only you can read.
+
+## Claude Desktop
+
+Desktop holds one sign-in at a time, so it switches with a restart:
+
+1. Quit Desktop.
+2. Run `claudectl desktop acme`.
+3. Start Desktop.
+
+This swaps the local MCP servers in Desktop's config. Each customer's servers are saved automatically when you switch away.
+
+Cloud connectors added on claude.ai belong to the signed-in account and follow it. If the customer uses a different Claude account, sign out and back in.
+
+**Not isolated:** Desktop's own Code tab uses Desktop's built-in Claude Code and login. Do isolated customer work in a terminal with claudectl.
+
+## Where things live
+
+Everything is in `~/.claudectl`, on every OS. On Windows this is deliberately not AppData: Microsoft Store Python redirects new files there into a private folder that Claude Code can't see.
+
+Each profile lives in `~/.claudectl/profiles/<name>/`:
+- `profile.json`: platform, models, how the key is stored
+- `config/`: Claude Code's own folder for this customer (login, MCP, skills, plugins, history, memory)
+- `desktop-mcp.json`: this customer's Claude Desktop MCP servers
+
+Set `CLAUDECTL_HOME` to put the data folder somewhere else.

claude_profile-1.0.2/README.md

@@ -0,0 +1,151 @@
+# claudectl
+
+Use Claude Code with a separate profile for each customer, on Windows, macOS and Linux. Each profile has its own:
+
+- sign-in or API key
+- AI platform
+- MCP servers
+- skills and plugins
+- session history and memory
+
+Customers can run side by side in separate terminals. Switching never touches a session that's already running, and one customer's Jira or Confluence server never shows up in another customer's session.
+
+claudectl doesn't change anything machine-wide. Your normal `claude` and `~/.claude` keep working exactly as before, and appear as the `default` profile.
+
+It's pure Python 3.10+ with no dependencies beyond the standard library.
+
+## Install
+
+From PyPI (the package is `claude-profile`, the command is `claudectl`):
+
+```bash
+pipx install claude-profile      # or: uv tool install claude-profile   or: pip install claude-profile
+claudectl install               # optional: adds the "Claude Profiles" Start menu picker on Windows
+```
+
+**Without Python:** download a standalone binary from [Releases](https://github.com/CloudOpsWorld/claude-profile/releases) and run it once with `install`, which puts it in `~/.local/bin`:
+- `claudectl-windows-amd64.exe`
+- `claudectl-macos-arm64`
+- `claudectl-linux-amd64`
+
+Each release has `SHA256SUMS` and build provenance you can check with `gh attestation verify <file> --repo CloudOpsWorld/claude-profile`.
+
+**From source:**
+
+```bash
+python claudectl/cli.py install
+```
+
+This copies the single file to `~/.claudectl/app` and puts a launcher in `~/.local/bin`.
+
+To remove claudectl, run `claudectl uninstall` (or `pipx uninstall claude-profile`). Your profiles are kept.
+
+## Daily use
+
+```bash
+claudectl add acme                 # guided: name, AI platform, key or sign-in, bind this folder
+cd ~/work/acme-repo
+claudectl                          # starts Claude Code as ACME, because the folder is bound
+claudectl tab globex               # new terminal tab locked to Globex
+claudectl acme --resume            # any claude arguments pass through
+claudectl mcp add jira -- npx -y <jira-mcp>   # goes into this folder's profile only
+claudectl list                     # profiles, bound folders, active profile, Desktop profile
+```
+
+- **Bound folders** pick the profile automatically. If you start a different profile inside a bound folder, claudectl asks before continuing.
+- **Everywhere else**, `claudectl` uses the active profile. Set it with `claudectl use <name>`.
+- **Every session shows its customer** in Claude Code's status line and in the tab title.
+- **On Windows**, tabs open in Windows Terminal with the customer's color. macOS uses Terminal.app. Linux uses the first terminal it finds: GNOME Terminal, Konsole, kitty, WezTerm, Alacritty or Xfce Terminal.
+
+## Import your existing setup
+
+```bash
+claudectl import --scan     # just show what's in your current Claude setup
+claudectl import            # guided: sort project folders into customer profiles
+```
+
+**What the scan finds:**
+- every project folder Claude has history for (worktrees are folded into their repo)
+- MCP servers, both user-wide and per-project
+- skills, agents, commands and output styles
+- your `CLAUDE.md`, plugins and preferences
+- Claude Desktop's MCP servers
+- leftovers from older switcher scripts: extra `~/.claude-*` config folders, system-wide `ANTHROPIC_*` variables, and lines in your PowerShell or shell profile
+
+It skips temporary folders, folders that no longer exist, your home folder and drive roots.
+
+**The guided import** suggests customers from your folder layout. `D:\work\acme\api` and `D:\work\acme\web` become one `acme` profile, tied to `D:\work\acme`. You can:
+- press Enter to accept each suggestion
+- type a name to rename it or merge it into another profile
+- press `k` to keep those folders in your default setup
+
+Then you pick:
+- the AI platform for each new profile
+- which profiles get which MCP servers
+- whether new profiles get your skills, `CLAUDE.md`, preferences and plugins (plugins are reinstalled cleanly in each profile)
+
+**It only copies.** Each project's history, memory, prompt history, trust settings and per-project MCP servers go into its profile. Your current setup isn't changed, so it's safe while Claude is running.
+
+**Your own sign-in, account details and caches are never copied into a customer profile.** The one exception: a `~/.claude-*` folder left by an older switcher is adopted whole, including its sign-in, because that sign-in belongs to the customer.
+
+You can also work from a file, which is handy for many folders or for repeating the import:
+
+```bash
+claudectl import --plan plan.json                  # write the suggestions to a file you can edit
+claudectl import --apply plan.json --dry-run       # show what would happen
+claudectl import --apply plan.json                 # copy
+claudectl import --apply plan.json --move          # copy, then take it out of the default setup
+```
+
+Running `--apply` again is safe: it never overwrites anything and doesn't duplicate history.
+
+**`--move`** removes the imported customer folders, history and MCP servers from your default setup:
+- It refuses while any Claude Code session is running, including Desktop's Code tab.
+- It backs up your config first.
+- It puts everything it removes in `~/.claudectl/import-backups/`.
+- Desktop's Code tab uses your default setup, so moved history no longer shows up there.
+
+`--from DIR` imports from another Claude config folder instead of `~/.claude`.
+
+## AI platforms
+
+| Platform | How it connects |
+|---|---|
+| Claude subscription: Pro, Max, Team, Enterprise | Browser sign-in on first start. You can lock it to the customer's org UUID. |
+| Anthropic API key | Pay per use. |
+| DeepSeek | Native Claude-compatible endpoint. |
+| OpenRouter | GPT, Gemini and others. Use this for OpenAI customers, with BYOK for their own OpenAI key. |
+| Any Claude-compatible URL | For example a LiteLLM proxy in front of a direct OpenAI key, Moonshot, Z.ai or a company gateway. |
+| AWS Bedrock, Google Vertex | Claude through the customer's own cloud account. |
+
+To add a platform, create `~/.claudectl/providers.json`: a JSON list of entries in the same shape as `BUILTIN_PROVIDERS` at the top of [claudectl/cli.py](claudectl/cli.py). An entry with an existing `id` replaces the built-in one. To change a profile's models, run `claudectl edit <name>`.
+
+**Where API keys are stored:**
+- **Windows:** encrypted with DPAPI, so only your Windows user can read them.
+- **macOS:** in your login Keychain.
+- **Linux:** in your keyring through `secret-tool`. Without a keyring, in a file only you can read.
+
+## Claude Desktop
+
+Desktop holds one sign-in at a time, so it switches with a restart:
+
+1. Quit Desktop.
+2. Run `claudectl desktop acme`.
+3. Start Desktop.
+
+This swaps the local MCP servers in Desktop's config. Each customer's servers are saved automatically when you switch away.
+
+Cloud connectors added on claude.ai belong to the signed-in account and follow it. If the customer uses a different Claude account, sign out and back in.
+
+**Not isolated:** Desktop's own Code tab uses Desktop's built-in Claude Code and login. Do isolated customer work in a terminal with claudectl.
+
+## Where things live
+
+Everything is in `~/.claudectl`, on every OS. On Windows this is deliberately not AppData: Microsoft Store Python redirects new files there into a private folder that Claude Code can't see.
+
+Each profile lives in `~/.claudectl/profiles/<name>/`:
+- `profile.json`: platform, models, how the key is stored
+- `config/`: Claude Code's own folder for this customer (login, MCP, skills, plugins, history, memory)
+- `desktop-mcp.json`: this customer's Claude Desktop MCP servers
+
+Set `CLAUDECTL_HOME` to put the data folder somewhere else.

claude_profile-1.0.2/RELEASING.md

@@ -0,0 +1,72 @@
+# Releasing claude-profile
+
+Publishing is fully automated via GitHub Actions: pushing a new version to `main`
+triggers a release.
+
+## Workflows
+
+| Workflow | Trigger | What it does |
+|----------|---------|--------------|
+| `.github/workflows/ci.yml` | push / PR to `main`/`master` | Test matrix (Ubuntu + macOS + Windows × Python 3.10–3.13), advisory ruff lint & mypy |
+| `.github/workflows/build.yml` | `workflow_call` / manual | Runs tests, builds standalone binaries (Linux, macOS, Windows via PyInstaller) and the wheel/sdist (`python -m build` + `twine check`) |
+| `.github/workflows/release.yml` | push to `main`/`master` | Detects a new version, tags it, builds artifacts, creates a GitHub Release, and publishes to PyPI |
+
+## How a release happens
+
+1. Bump the version in **both** `pyproject.toml` and `claudectl/__init__.py`
+   (the release workflow fails if they disagree).
+2. Commit and push to `main`.
+3. `release.yml` will:
+   - see the version has no matching `vX.Y.Z` git tag,
+   - create and push that tag,
+   - build binaries + wheel/sdist,
+   - create a GitHub Release with the binaries and package attached,
+   - publish the wheel/sdist to PyPI as `claude-profile`.
+
+If the tag already exists, the release is skipped — so pushing unrelated commits
+never re-releases.
+
+## One-time PyPI setup (Trusted Publishing — recommended)
+
+No API token required. On PyPI, signed in as an owner of the **CloudOpsWorld**
+organization:
+
+1. Go to **Your organizations → CloudOpsWorld → Publishing → Add a new pending
+   publisher** (or **Your account → Publishing** for a personal project) with:
+   - PyPI project name: `claude-profile`
+   - Owner: `CloudOpsWorld`
+   - Repository: `claude-profile`
+   - Workflow name: `release.yml`
+   - Environment: `pypi`
+2. In the GitHub repo, the **Environment** named `pypi` must exist
+   (Settings → Environments) — optionally add required reviewers for a manual
+   approval gate before publish.
+
+That's it: `release.yml` requests an OIDC token (`id-token: write`) and PyPI
+trusts it. The first successful publish creates the project under the org.
+
+### Alternative: API token
+
+If you prefer a token, add a repository secret `PYPI_API_TOKEN` and uncomment the
+`password:` line in the `publish-pypi` job of `release.yml`.
+
+## Testing the pipeline first
+
+- Run **Build** manually (Actions → Build → Run workflow) to confirm binaries and
+  the package build without cutting a release.
+- Optionally point at **TestPyPI** first by adding `repository-url:
+  https://test.pypi.org/legacy/` to the publish step.
+
+## Re-running a failed publish
+
+If the publish job failed (for example because the pending publisher wasn't set
+up yet), fix the cause and use **Re-run failed jobs** on that workflow run. The
+tag and GitHub Release already exist, and `skip-existing: true` makes re-runs safe.
+
+## Local dry run
+
+```bash
+pip install build twine
+python -m build
+twine check dist/*
+```

claude_profile-1.0.2/claude_profile.egg-info/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: claude-profile
+Version: 1.0.2
+Summary: Per-customer profiles for Claude Code and Claude Desktop: separate logins, AI platforms, MCP servers, skills and history, side by side.
+Author: claude-profile contributors
+License: MIT
+Project-URL: Homepage, https://github.com/CloudOpsWorld/claude-profile
+Project-URL: Repository, https://github.com/CloudOpsWorld/claude-profile
+Project-URL: Issues, https://github.com/CloudOpsWorld/claude-profile/issues
+Keywords: claude,claude-code,claude-desktop,anthropic,profiles,mcp,deepseek,openrouter,cli
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=9.1.1; extra == "dev"
+Requires-Dist: ruff>=0.15.21; extra == "dev"
+Requires-Dist: mypy>=2.3.0; extra == "dev"
+Requires-Dist: build>=1.5.1; extra == "dev"
+Dynamic: license-file
+
+# claudectl
+
+Use Claude Code with a separate profile for each customer, on Windows, macOS and Linux. Each profile has its own:
+
+- sign-in or API key
+- AI platform
+- MCP servers
+- skills and plugins
+- session history and memory
+
+Customers can run side by side in separate terminals. Switching never touches a session that's already running, and one customer's Jira or Confluence server never shows up in another customer's session.
+
+claudectl doesn't change anything machine-wide. Your normal `claude` and `~/.claude` keep working exactly as before, and appear as the `default` profile.
+
+It's pure Python 3.10+ with no dependencies beyond the standard library.
+
+## Install
+
+From PyPI (the package is `claude-profile`, the command is `claudectl`):
+
+```bash
+pipx install claude-profile      # or: uv tool install claude-profile   or: pip install claude-profile
+claudectl install               # optional: adds the "Claude Profiles" Start menu picker on Windows
+```
+
+**Without Python:** download a standalone binary from [Releases](https://github.com/CloudOpsWorld/claude-profile/releases) and run it once with `install`, which puts it in `~/.local/bin`:
+- `claudectl-windows-amd64.exe`
+- `claudectl-macos-arm64`
+- `claudectl-linux-amd64`
+
+Each release has `SHA256SUMS` and build provenance you can check with `gh attestation verify <file> --repo CloudOpsWorld/claude-profile`.
+
+**From source:**
+
+```bash
+python claudectl/cli.py install
+```
+
+This copies the single file to `~/.claudectl/app` and puts a launcher in `~/.local/bin`.
+
+To remove claudectl, run `claudectl uninstall` (or `pipx uninstall claude-profile`). Your profiles are kept.
+
+## Daily use
+
+```bash
+claudectl add acme                 # guided: name, AI platform, key or sign-in, bind this folder
+cd ~/work/acme-repo
+claudectl                          # starts Claude Code as ACME, because the folder is bound
+claudectl tab globex               # new terminal tab locked to Globex
+claudectl acme --resume            # any claude arguments pass through
+claudectl mcp add jira -- npx -y <jira-mcp>   # goes into this folder's profile only
+claudectl list                     # profiles, bound folders, active profile, Desktop profile
+```
+
+- **Bound folders** pick the profile automatically. If you start a different profile inside a bound folder, claudectl asks before continuing.
+- **Everywhere else**, `claudectl` uses the active profile. Set it with `claudectl use <name>`.
+- **Every session shows its customer** in Claude Code's status line and in the tab title.
+- **On Windows**, tabs open in Windows Terminal with the customer's color. macOS uses Terminal.app. Linux uses the first terminal it finds: GNOME Terminal, Konsole, kitty, WezTerm, Alacritty or Xfce Terminal.
+
+## Import your existing setup
+
+```bash
+claudectl import --scan     # just show what's in your current Claude setup
+claudectl import            # guided: sort project folders into customer profiles
+```
+
+**What the scan finds:**
+- every project folder Claude has history for (worktrees are folded into their repo)
+- MCP servers, both user-wide and per-project
+- skills, agents, commands and output styles
+- your `CLAUDE.md`, plugins and preferences
+- Claude Desktop's MCP servers
+- leftovers from older switcher scripts: extra `~/.claude-*` config folders, system-wide `ANTHROPIC_*` variables, and lines in your PowerShell or shell profile
+
+It skips temporary folders, folders that no longer exist, your home folder and drive roots.
+
+**The guided import** suggests customers from your folder layout. `D:\work\acme\api` and `D:\work\acme\web` become one `acme` profile, tied to `D:\work\acme`. You can:
+- press Enter to accept each suggestion
+- type a name to rename it or merge it into another profile
+- press `k` to keep those folders in your default setup
+
+Then you pick:
+- the AI platform for each new profile
+- which profiles get which MCP servers
+- whether new profiles get your skills, `CLAUDE.md`, preferences and plugins (plugins are reinstalled cleanly in each profile)
+
+**It only copies.** Each project's history, memory, prompt history, trust settings and per-project MCP servers go into its profile. Your current setup isn't changed, so it's safe while Claude is running.
+
+**Your own sign-in, account details and caches are never copied into a customer profile.** The one exception: a `~/.claude-*` folder left by an older switcher is adopted whole, including its sign-in, because that sign-in belongs to the customer.
+
+You can also work from a file, which is handy for many folders or for repeating the import:
+
+```bash
+claudectl import --plan plan.json                  # write the suggestions to a file you can edit
+claudectl import --apply plan.json --dry-run       # show what would happen
+claudectl import --apply plan.json                 # copy
+claudectl import --apply plan.json --move          # copy, then take it out of the default setup
+```
+
+Running `--apply` again is safe: it never overwrites anything and doesn't duplicate history.
+
+**`--move`** removes the imported customer folders, history and MCP servers from your default setup:
+- It refuses while any Claude Code session is running, including Desktop's Code tab.
+- It backs up your config first.
+- It puts everything it removes in `~/.claudectl/import-backups/`.
+- Desktop's Code tab uses your default setup, so moved history no longer shows up there.
+
+`--from DIR` imports from another Claude config folder instead of `~/.claude`.
+
+## AI platforms
+
+| Platform | How it connects |
+|---|---|
+| Claude subscription: Pro, Max, Team, Enterprise | Browser sign-in on first start. You can lock it to the customer's org UUID. |
+| Anthropic API key | Pay per use. |
+| DeepSeek | Native Claude-compatible endpoint. |
+| OpenRouter | GPT, Gemini and others. Use this for OpenAI customers, with BYOK for their own OpenAI key. |
+| Any Claude-compatible URL | For example a LiteLLM proxy in front of a direct OpenAI key, Moonshot, Z.ai or a company gateway. |
+| AWS Bedrock, Google Vertex | Claude through the customer's own cloud account. |
+
+To add a platform, create `~/.claudectl/providers.json`: a JSON list of entries in the same shape as `BUILTIN_PROVIDERS` at the top of [claudectl/cli.py](claudectl/cli.py). An entry with an existing `id` replaces the built-in one. To change a profile's models, run `claudectl edit <name>`.
+
+**Where API keys are stored:**
+- **Windows:** encrypted with DPAPI, so only your Windows user can read them.
+- **macOS:** in your login Keychain.
+- **Linux:** in your keyring through `secret-tool`. Without a keyring, in a file only you can read.
+
+## Claude Desktop
+
+Desktop holds one sign-in at a time, so it switches with a restart:
+
+1. Quit Desktop.
+2. Run `claudectl desktop acme`.
+3. Start Desktop.
+
+This swaps the local MCP servers in Desktop's config. Each customer's servers are saved automatically when you switch away.
+
+Cloud connectors added on claude.ai belong to the signed-in account and follow it. If the customer uses a different Claude account, sign out and back in.
+
+**Not isolated:** Desktop's own Code tab uses Desktop's built-in Claude Code and login. Do isolated customer work in a terminal with claudectl.
+
+## Where things live
+
+Everything is in `~/.claudectl`, on every OS. On Windows this is deliberately not AppData: Microsoft Store Python redirects new files there into a private folder that Claude Code can't see.
+
+Each profile lives in `~/.claudectl/profiles/<name>/`:
+- `profile.json`: platform, models, how the key is stored
+- `config/`: Claude Code's own folder for this customer (login, MCP, skills, plugins, history, memory)
+- `desktop-mcp.json`: this customer's Claude Desktop MCP servers
+
+Set `CLAUDECTL_HOME` to put the data folder somewhere else.

claude_profile-1.0.2/claude_profile.egg-info/SOURCES.txt

@@ -0,0 +1,17 @@
+LICENSE
+MANIFEST.in
+README.md
+RELEASING.md
+pyproject.toml
+claude_profile.egg-info/PKG-INFO
+claude_profile.egg-info/SOURCES.txt
+claude_profile.egg-info/dependency_links.txt
+claude_profile.egg-info/entry_points.txt
+claude_profile.egg-info/requires.txt
+claude_profile.egg-info/top_level.txt
+claudectl/__init__.py
+claudectl/__main__.py
+claudectl/cli.py
+scripts/claudectl_entry.py
+scripts/demo.ps1
+tests/test_claudectl.py

claude_profile-1.0.2/claude_profile.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

claude_profile-1.0.2/claude_profile.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+claudectl = claudectl.cli:main

claude_profile-1.0.2/claude_profile.egg-info/requires.txt

@@ -0,0 +1,6 @@
+
+[dev]
+pytest>=9.1.1
+ruff>=0.15.21
+mypy>=2.3.0
+build>=1.5.1

claude_profile-1.0.2/claude_profile.egg-info/top_level.txt

@@ -0,0 +1 @@
+claudectl

claude_profile-1.0.2/claudectl/__init__.py

@@ -0,0 +1,3 @@
+"""claudectl - per-customer profiles for Claude Code and Claude Desktop."""
+
+__version__ = "1.0.2"

claude_profile-1.0.2/claudectl/__main__.py

@@ -0,0 +1,3 @@
+from claudectl.cli import main
+
+main()