multi-profile-plugins

v1.3.2

Understand and diagnose config-profile isolation on a machine running several Claude Code CLAUDE_CONFIG_DIR profiles or several Codex CODEX_HOME profiles, and report how much usage-limit budget each profile has consumed. Explains why Claude Code profiles that share a plugins store hit recurring "corrupted installLocation" errors and cross-profile plugin deletion, and why a Codex profile seeded by copying config.toml keeps reading the home it was copied from, including an MCP server that re-enters it. Ships a read-only health-check script for each, a usage-limit report covering every Claude Code profile and Codex home with reset times and Codex reset-voucher counts and expiry -- installable on PATH as `code-limit` -- and documents the reverse-engineered Claude Code CLI validation and garbage-collection mechanism behind the first.

Claude Code3 Skills

By Lazy Ants0 GitHub starsUpdated 2 weeks ago

Directory evidence

Runtimes: Claude Code
Parsed components: 3 skill or MCP entries
Source updated: Sep 5, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install multi-profile-plugins for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install multi-profile-plugins@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/lazyants/claude-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/multi-profile-plugins/.

Plugin files

plugins/multi-profile-plugins/

├── .claude-plugin/plugin.json
├── skills/code-limits/SKILL.md
├── skills/multi-profile-codex/SKILL.md
└── skills/multi-profile-plugins/SKILL.md

Included Skills3

code-limitsskills/code-limits/SKILL.md

How much of a usage-limit window is left, when it resets, and which Claude Code profile or Codex home is close to exhausted, across every profile on this machine -- every discovered Claude Code profile under `~/.claude*` (`CLAUDE_CONFIG_DIR`) and every discovered Codex home under `~/.codex*` (`CODEX_HOME`). Use when asked how much usage-limit budget is left, when a five-hour or weekly window resets, which profile or account is nearly out, or how many Codex "usage limit reset" vouchers remain. Ships `scripts/report_limits.py`, installable on PATH as `code-limit`, one table covering both CLIs: Claude Code read from its on-disk usage cache by default (or live with `--live`) and Codex read live over `codex app-server`'s `account/rateLimits/read` JSON-RPC call. Not the sibling `multi-profile-plugins` skill (plugin-store topology, `installLocation` errors) or `multi-profile-codex` (`CODEX_HOME` architecture, seeding, config pins) -- this one is only about usage-limit consumption and reset timing.

multi-profile-codexskills/multi-profile-codex/SKILL.md

How the Codex CLI stores credentials and config when several CODEX_HOME profiles run on one machine — commonly a base `~/.codex` plus alternates such as `~/.codex2` or `~/.codex3`, one per OpenAI account. Use when setting up or seeding a second Codex profile, choosing which CODEX_HOME an invocation should target, wiring a per-profile launcher, or debugging a profile that reads another profile's tree — sessions or plugins showing up under the wrong account, an MCP server escaping into the base home, or two profiles that turn out to share one usage pool.

multi-profile-pluginsskills/multi-profile-plugins/SKILL.md

How Claude Code stores plugins and config when multiple CLAUDE_CONFIG_DIR profiles are in use — commonly a base `~/.claude` plus one or more extras such as `~/.claude2`, `~/.claude3`, or a separate profile the desktop app runs independently of the CLI. Use when running any `claude plugin …` CLI op (install/update/ remove a plugin, add or refresh a marketplace) in a multi-profile setup, choosing which CLAUDE_CONFIG_DIR to target, debugging a "corrupted installLocation" error, or reasoning about why a plugin or marketplace appears — or gets GC-deleted — in one profile but not another.

Plugin manifests1

plugins/multi-profile-plugins/.claude-plugin/plugin.json

{
  "name": "multi-profile-plugins",
  "description": "Understand and diagnose config-profile isolation on a machine running several Claude Code CLAUDE_CONFIG_DIR profiles or several Codex CODEX_HOME profiles, and report how much usage-limit budget each profile has consumed. Explains why Claude Code profiles that share a plugins store hit recurring \"corrupted installLocation\" errors and cross-profile plugin deletion, and why a Codex profile seeded by copying config.toml keeps reading the home it was copied from, including an MCP server that re-enters it. Ships a read-only health-check script for each, a usage-limit report covering every Claude Code profile and Codex home with reset times and Codex reset-voucher counts and expiry -- installable on PATH as `code-limit` -- and documents the reverse-engineered Claude Code CLI validation and garbage-collection mechanism behind the first.",
  "version": "1.3.2",
  "author": {
    "name": "Lazy Ants"
  },
  "homepage": "https://github.com/lazyants/claude-plugins",
  "keywords": [
    "claude-code",
    "codex",
    "plugins",
    "multi-profile",
    "config-dir",
    "claude-config-dir",
    "codex-home",
    "corrupted-installlocation",
    "marketplace",
    "diagnostics",
    "profiles",
    "usage-limits",
    "rate-limits"
  ],
  "skills": "./skills/"
}