wrangler-accounts

wrangler-accounts

AWS-style multi-account convenience for Cloudflare Wrangler. Run commands against different Cloudflare accounts in parallel shells without switching global state.

wrangler-accounts login work                   # first-time setup (isolated)
wrangler-accounts default work                 # set persistent default
wrangler-accounts deploy                       # uses default profile
wrangler-accounts --profile personal deploy
wrangler-accounts exec personal -- npm run release

Two shells side by side, two different Cloudflare accounts, zero interference:

# terminal 1
wrangler-accounts --profile work tail my-worker

# terminal 2
wrangler-accounts --profile personal dev

Claude Code users (recommended)

Install the marketplace and plugin first:

/plugin marketplace add leeguooooo/wrangler-accounts
/plugin install wrangler-accounts@leeguoo-tools

The plugin bundles the wrangler-accounts skill plus a Bash PreToolUse hook, so Claude Code can learn the workflow and block raw wrangler calls before they bypass your local profile isolation. No manual settings.json editing is required.

The plugin does not install the CLI binary. Keep the npm package on your PATH:

npm i -g @leeguoo/wrangler-accounts

The guard only blocks direct wrangler ... Bash commands when all of these are true:

• wrangler-accounts is installed on PATH
• at least one local profile is configured
• the current directory looks like a Cloudflare project (wrangler.toml, wrangler.json, or wrangler.jsonc) or Cloudflare API env vars are set

If you explicitly want raw wrangler, bypass the hook for that command:

NOWRANGLER_ACCOUNTS_GUARD=1 wrangler deploy

Upgrading from the skills.sh install

If you previously installed this skill via npx skills add leeguooooo/wrangler-accounts, remove that standalone copy after installing the plugin — otherwise Claude Code's slash command picker shows two identical /wrangler-accounts entries (one from the skills.sh directory, one from the plugin):

npx skills remove wrangler-accounts
# or, if the CLI is missing: rm -rf ~/.agents/skills/wrangler-accounts

Then run /reload-plugins and confirm only one entry remains.

What it does

Every execution runs wrangler inside a per-invocation shadow HOME — a temporary directory that mirrors most of your real home, except .wrangler/config/default.toml is a symlink pointing at the saved profile's config. Token refreshes flow back to the profile automatically. Nothing touches your real ~/.wrangler. Two parallel invocations get two independent shadow HOMEs.

Install

If you do not use Claude Code plugins, install the CLI binary and the mirrored skills.sh skill separately:

# 1. The CLI (always required)
npm i -g @leeguoo/wrangler-accounts

# 2. The AI agent skill mirror (recommended if you use Cursor / Codex / Gemini CLI / etc.)
npx skills add leeguooooo/wrangler-accounts -g -y

The CLI works standalone — you can skip step 2 if you don't use an AI coding agent. The skill is just markdown documentation the AI reads; it cannot run anything without the CLI installed.

Why two steps?

	Installs	For
npm i -g @leeguoo/wrangler-accounts	The wrangler-accounts executable onto your PATH	Your shell
npx skills add leeguooooo/wrangler-accounts	SKILL.md (markdown) into your AI agent's skills directory	Your AI agent to read

The AI will tell you to run commands like wrangler-accounts --profile work deploy; without step 1 those commands fail with "command not found".

skills.sh mirror — more options

The repo keeps a mirrored Agent Skill at skills/wrangler-accounts/SKILL.md for skills.sh. Claude Code users should prefer the plugin marketplace flow above; other agents can keep using skills.sh to install the same guidance markdown into their own skill directories.

npx skills add leeguooooo/wrangler-accounts -g -y        # user-global, non-interactive
npx skills add leeguooooo/wrangler-accounts              # project-scoped, interactive
npx skills add leeguooooo/wrangler-accounts -a claude-code cursor   # specific agents only
npx skills add leeguooooo/wrangler-accounts --list       # preview without installing

After both are installed, ask your AI agent something like "deploy my worker to the work account" or "set up a new Cloudflare profile" and the skill will guide it through the right commands.

Usage

wrangler-accounts <wrangler-args...>            # uses default profile
wrangler-accounts --profile <name> <wrangler-args...>
wrangler-accounts -p <name> <wrangler-args...>
WRANGLER_PROFILE=<name> wrangler-accounts <wrangler-args...>

wrangler-accounts exec <name>                   # interactive subshell
wrangler-accounts exec <name> -- <cmd> [args]   # one command