Power Claude — Spend less. Run faster. Never stall on Claude Code.

🎉 Due to popular demand — now on the VS Code Marketplace, Open VSX & npm

Power Claude has been available direct from neural-llm.com since December 2025. By popular request, it's now one click away in your editor's marketplace too — the same battle-tested tool, now wherever you install extensions.

Simple enough for the vibe-coder novice, powerful enough for the most seasoned dev.

⚡ Claude Code feeling slow lately? You're not imagining it — and you don't have to live with it. Pool the Claude accounts you already have for ~N× the rate‑limit windows — 5 Pro accounts match one Max‑20×'s session ceiling for $115+/mo back.

Save $115+/mo on Claude Code — 5 pooled Pro accounts equal one Max‑20×'s 5‑hour session token ceiling (~220k) for ~58% less ($83/mo on annual billing vs $200). Claude Code didn't get slower — your single account did. Heavy sub‑agent fan‑out hammers one account's per‑minute limits, every 429 is dead time, and you wait. Power Claude pools the Claude Pro accounts you already pay for and routes every request to the account with the most headroom — so you get ~N× the throughput (each pooled account is its own independent rate‑limit window) and a 429 never stalls the session (it flips to the healthiest account instantly, no waiting on Retry‑After). A watchdog revives crashed, stalled, and rate‑limited sessions in the same tab — while Token Saver trims wasteful, repetitive tool‑output token burn and Token Tree surfaces where your tokens leak, with your real savings shown live. Cheaper, faster, and it runs through the wall — here's exactly how. ↓

code --install-extension neural-llm.power-claude

Every way to get Power Claude — same extension, pick whatever fits your editor and workflow:

Channel	Best for	Get it
VS Code Marketplace	VS Code — one click	code --install-extension neural-llm.power-claude
Open VSX	Cursor · VSCodium · Gitpod · Windsurf	cursor --install-extension neural-llm.power-claude
npm (CLI)	any terminal · CI	npm install -g power-claude
Direct .vsix	air-gapped · manual · pinned version	code --install-extension power-claude-<version>.vsix
neural-llm.com	downloads · docs · account	neural-llm.com

Power Claude is an independent extension by Neural-LLM. It is not affiliated with Anthropic; "Claude" is a trademark of Anthropic, PBC. Power Claude interoperates with Claude Code's local files — it is third-party tooling.

---

Stop overpaying for Claude capacity

You're hitting the wall every afternoon. The obvious fix — upgrade to Max, or start paying per-token API rates — costs a multiple of what you pay now. Power Claude gives you a cheaper path to the same headroom.

Pool the accounts you already have. Each Claude.ai Pro or Max subscription is a completely independent organization on Anthropic's side, each with its own 5-hour, 7-day, per-minute-token (TPM), and per-minute-request (RPM) rate-limit windows. There is no shared pool between them. Power Claude uses them all, all the time — so N independent accounts give you roughly N× the capacity on every one of those windows, at the price of N Pro subscriptions instead of one Max plan or a metered API bill.

• 📅 Annual billing is ~17% cheaper. Claude Pro is $20/mo month‑to‑month, but $200/yr billed annually — an effective $16.67/mo, ~17% less. Annual Pro is the cheapest seat to pool.
• 💰 Apples‑to‑apples: 5 Pro = one Max‑20×'s session ceiling, for ~58% less. The wall you hit mid‑task is the 5‑hour session token ceiling. One Claude Max‑20× tops out around ~220k tokens per session; 5 pooled Pro accounts (~44k each) reach the same ~220k — for a fraction of the price, and with 5 independent windows instead of 1:

	1 × Claude Max‑20×	5 × pooled Pro (annual)
5‑hour session token ceiling	~220k	~220k (5 × ~44k) — same
Independent rate‑limit windows	1	5
Monthly cost	$200	$83 → save $117/mo (58%)

Honest basis: Anthropic publishes plan multipliers (Max‑20× = "20× Pro") and prices, not exact token caps — the ~44k/~220k figures are consistent 2026 estimates. That 20× is Max‑20×'s weekly sustained volume; the 5× here is the per‑session ceiling — the mid‑task wall. Power Claude's own subscription is $12/mo, shown separately, never folded into the figures above. Your dashboard runs this against your real pool, so it's verifiable — not a slogan.

• 📊 See the savings locally. Per-account, per-model $/token tracking shows your effective cost under your current subscription tiers versus what the same work would have cost at pay-per-token API rates — so the savings aren't a marketing claim, they're a number in your dashboard.
• 🎯 Know when an upgrade is actually worth it. The cap-hit recommender flags exactly when upgrading a plan would eliminate the throttling that regularly stalls your workflow — and stays quiet when it wouldn't. No upsell guesswork.

Why it works: Claude.ai Pro and Max subscriptions each carry their own 5-hour, 7-day, TPM, and RPM rate-limit windows. Accounts are completely independent organizations on Anthropic's side — there is no shared pool. Power Claude simply uses them all, all the time. It does not bypass, circumvent, or violate any Anthropic rate limit or term of service — every account stays within its own published limits.

All cost math runs locally. Power Claude reads Claude Code's own local state and session transcripts — the same files Claude Code writes. No token counts, transcripts, or usage data leave your machine.

---

Power Claude vs. vanilla Claude Code

	Claude Code alone	With Power Claude
Rate limit (429)	Wait for the 5-hour / weekly window to reset	Auto-rotates to the account with the most headroom — N accounts ≈ N× throughput
Cost of more capacity	Upgrade to Max, or pay per-token API rates	Pool only the Pro accounts your usage needs — N accounts ≈ N× a single account, in N independent windows
Cost visibility	None built in	Per-account, per-model $/token tracking + subscription-vs-API comparison
Multiple accounts	Manual logout / login each time	One pool, automatic routing (Balanced Mode scores every account per request)
Concurrent sessions	Serialized against one account	Spread across the pool — a round finishes ~N× faster
Crashed / stalled session	Notice late, restart by hand, lose context	Watchdog detects crashed/stalled/rate-limited sessions + one-click auto-resume
Session history	Hunt through JSONL transcripts + git diffs	Insight Graph: files touched, model, cost, completion status per session
AI-edit blame	None	Editor-gutter blame per Claude session (runs alongside GitLens)
Where your data goes	—	All local — no prompts or code ever leave your machine
Editors	VS Code, Cursor	VS Code, Cursor, and a CLI — one shared ~/.power-claude/

---

Core capabilities

🔄 Multi-account rotation + smart 429 routing

Connect personal, team, and project-specific Claude accounts. Power Claude watches rate limits in real time via the Claude Code state directory that Claude Code writes itself. When the active account hits a cap:

1. The Stop hook fires and Power Claude detects the rate-limit signal
2. The soonest-recovering account is activated automatically
3. The interrupted session resumes in the same VS Code tab — same context, same conversation, no retyping

Smart 429 routing is the proactive half. When an account returns 429 — whether a per-minute throttle or a hard quota signal — the proxy tries a healthy alternate first instead of sleeping up to 120 seconds on Retry-After. The throttled account is put in cooldown so the selector can't pick it again until Anthropic says it's ready. Anti-ping-pong is structural, not a heuristic: each 429 marks its account out for its Retry-After window, so the proxy can't bounce between two throttled accounts. If the entire pool is throttled at once, it falls back to the existing wait-and-retry path on the least-bad account — you never end up worse off than before.

The status bar shows a live count of healthy / cooling / blocked accounts and the cumulative N throttle waits avoided. The accounts dashboard shows cooldown ETAs and lets you manually activate, refresh, or re-authenticate any account.

<img src="https://raw.githubusercontent.com/neural-llm-io/power-claude/main/media/marketplace/08-balanced-mode-status-bar.png" alt="Power Claude status bar showing the live "Balanced · 3 accounts · ~3× throughput" indicator with per-account health dots." width="100%">

🗂️ Account groups (isolated context)

Partition Claude accounts into named groups (Work / Personal / clients) with isolated projects/memory trees so context does not bleed across roles.

• Create groups in the dashboard (Profiles → Account groups) or pc scope create
• Drag accounts between groups, or pc scope add / pc scope move
• Use this group / pc scope use selects the active set for new work
• Credentials stay private per account — groups organize membership and local context only

⚡ Power Mode — N× throughput

Multi-account rotation reacts to exhaustion. Power Mode is proactive: every request is routed to the least-busy account simultaneously, so all your accounts fill in parallel instead of draining one before moving to the next. With three accounts you get an effective ~3× ceiling on each independent 5h / 7d / TPM / RPM window — and the per-minute throttling that used to choke single-account streaming during heavy sub-agent fan-out simply doesn't happen.

Mode	How it works	Best for
Standard rotation	Stays on one account until it exhausts, then switches	Light to moderate usage
Power Mode	Every request goes to the least-loaded account	Heavy / continuous coding sessions

The status bar shows ⚡ Balanced [3] ~3× while active, so you can see the multiplier at a glance. Enable from the Power Claude Settings panel in one click — no CLI, no config files. Or via CLI: power-claude balanced on.

⏱ Runout Forecaster — see the wall coming hours in advance

Power Mode and smart 429 routing prevent most rate-limit hits, but they can't stretch your subscriptions past their real limit. The Runout Forecaster watches utilization across every account and projects, at your current burn rate, whether you'll exhaust capacity before the 5-hour or 7-day windows reset.

State	Banner
Safe	green — "Pool safe through next reset (~3h 41m)"
Some accounts at risk	amber — "3 of 12 accounts at risk"
Pool exhaustion imminent	red — "Pool exhausts in ~28m"

Each account row also gets a tiny per-account ETA chip (✓ safe, ETA 1h 47m, ETA 14m) so you can spot the bottleneck without opening drawers.

The math is honest: reset times come from Anthropic's authoritative rate-limit headers, so the "will I make it before reset?" half of the calculation is exact. Only burn rate is estimated, from a rolling sample buffer of the last 30 minutes of utilization observations. When there isn't yet enough data to project (first ~2 minutes after activation, or no activity), the banner is suppressed and the chips show —.

↻ Auto-resume + resilience watchdog + Auto-Resume Nudges

Rate limits aren't the only thing that kills a session. Process kills, OOM events, IDE crashes, network drops mid-tool-call, and sessions that ended cleanly but left work unfinished all used to leave you with a stale tab and a manual recovery.

The watchdog polls every 30 seconds and applies four detection rules:

Trigger	Signal	What it means
Heartbeat-stale	No lifecycle:heartbeat in N seconds AND JSONL idle	Process kill, OOM, IDE crash, or network drop
Tool-truncation	Last assistant record is stop_reason: tool_use with no follow-up	Died mid-tool-call
Ended with pending tasks	Stopped cleanly but task items still pending	Session said "done" but work remains
Rate-limit	pending-recovery.json written by Stop hook	Standard rate-limit rotation

When the watchdog fires, Power Claude surfaces a one-click QuickPick with a reason-aware resume prompt — each death type gets tailored wording so the agent picks up with the right context.

Auto-Resume Nudges catch the more annoying case: sessions that stop politely when they should keep going. Claude pauses to ask "want me to continue?", offers a three-option menu when one option is obvious, or tells you to run a command it could have run itself. A family of toggleable detectors fires on every Stop event; when a pattern matches and no hard-stop veto fires (auth failure, missing credential, destructive op pending, approval gate), the Stop hook re-issues the turn with a targeted corrective prompt:

Default-on nudge	What it catches	What the agent sees back
ask-permission-to-continue	"Want me to continue?" / "Should I keep going?"	"Continue the work. Don't ask permission for obvious next steps."
offer-multi-choice	"Three reasonable next moves — 1) … 2) … 3) … which?"	"Pick the most obvious option and proceed."
tell-user-to-do-work	"You can run X to verify" / "You'll need to deploy"	"You have the tools to do this yourself."
pseudo-checkpoint	"Good stopping point" / "Let's pause here" with no reason	"There's no reason to pause. Continue to the next concrete deliverable."

Four more nudges ship opt-in for aggressive cases. A shadow mode logs every would-fire decision without resuming so you can audit before going live, and a loop guard caps consecutive nudges at 3. An optional LLM fallback (off by default; Haiku 4.5 when on) handles ambiguous stops the deterministic catalog missed — bounded to one ~128-token classification call per Stop, empirically ~3% of stops. The catalog lives at ~/.power-claude/config/nudges.json; edit it directly to tune patterns.

🩹 Session Actions — one-click recovery, right on the line that broke

When a turn dies with "Prompt is too long", you don't have to copy context into a fresh chat by hand. Power Claude detects the error on the chat line and injects a branded Heal button right there — click it and the session is trimmed and resumed automatically (the same trim-and-resume recovery the watchdog uses), no retyping.

Heal is the first of a family of Session Actions — recovery actions matched to how a session got stuck:

Action	When it appears	What it does
Heal	"Prompt is too long" / compaction thrash	Trim the conversation and resume in a fresh session
Unstick	Repeating tool loop	Fork from the last good checkpoint
Revive	Crashed / abandoned	Fork from the last good checkpoint
Re-run tool	Truncated mid tool-call	Re-issue the tool call
Finish tasks	Stopped with TODOs pending	Resume and inject the pending tasks
Resume	Idle / stuck after a rate-limit window	Plain resume
Repair turn	Wedged thinking turn (HTTP 400 on resume)	Trim the orphaned turn

Every action is available three ways: the inline button on the chat line, the Power Claude: Session Actions command (pick a session → pick an action), and the CLI (pc session action heal <session-id>). Each action is settings-gated (powerClaude.sessionActions.*) and its recovery strategy is configurable. Manual by default — you stay in control.

📊 Insight Graph + cost analytics + editor-gutter blame

After a long session, you want to know: What did it change? Which files? What model, and what did it cost? Did it finish? Today you answer those by hunting through JSONL transcripts and git diffs. Power Claude answers them in one click, rendering your session history as a commit-graph-style lane view — the visual language GitLens made familiar for git, applied to AI coding sessions.

Each row is a session, carrying a model badge (with version), total cost, files-changed count, the account that handled it, and a completion status (done / pending / untracked). Click any session to expand the full detail without leaving VS Code:

• Files panel — every file read, written, or edited, with per-file diff vs the session's git snapshot, op-type counts, and timestamps
• Sub-agents — forked agents appear as child lanes linked to the parent
• Hooks fired — which Claude Code hook scripts ran, with exit codes and timing
• Rate-limit events — when the session hit a cap, which account it rotated to, and the cooldown length
• Plans drafted and commits authored — plan-mode artifacts and every git commit, clickable to open the diff
• Multi-track timeline — tool calls, hook firings, model switches, and rate-limit events on one synchronized time axis

Cost analytics track token consumption and dollar cost per session, per account, and per model with plan-tier-aware math: per-account breakdowns by model with daily / weekly / monthly rollups, anchor markers showing exactly when caps were hit, the cap-hit upgrade recommender, and your subscription savings versus pay-per-token API rates.

Inline session blame annotates each region of any open file with the Claude session that last touched it — exactly like git blame, but for AI editing activity. Hover for the session summary (date, model, cost, completion status); click to jump to the full detail view. It runs alongside GitLens in a separate gutter column with distinct visual language, so the two never conflict.

🎯 Preserve-Focus Fix — stop Claude Code from yanking your cursor

You're typing in a file. Claude finishes a response. Suddenly your cursor jumps to the Claude panel and your keystrokes land in the wrong place — or you accidentally accept a pending action because your finger was already on Enter.

This is anthropics/claude-code#32726 — open since early 2026, no shipping fix. The Claude Code VS Code extension calls WebviewPanel.reveal() without preserveFocus: true on six code paths. Power Claude ships the patch Anthropic hasn't:

• Two settings — powerClaude.preserveFocusFix.enabled (default OFF — opt in once) and powerClaude.preserveFocusFix.autoRunOnUpgrade (default ON). Flip the first to true, reload the window, and the focus-steal is gone.
• Six surgical patches to the installed extension.js, anchored on stable string literals; after every Claude Code upgrade Power Claude detects the changed mtime and re-patches automatically.
• Idempotent and reversible — a sentinel comment makes re-runs a no-op, and a one-shot .preserve-focus.orig backup beside each patched file lets you undo cleanly.
• Manual command — Power Claude: Re-apply Preserve-Focus Patch to Claude Code Extension for the rare case the auto-detector misses an upgrade.

If Anthropic ships the proper upstream fix, you'll uninstall this in one toggle.

---

🎨 Purple Scrollbars — Power Claude's brand, on your scrollbars

A small one: Power Claude themes VS Code's scrollbars in its own brand violet, on by default.

• One setting — powerClaude.scrollbarTheme.enabled (default ON). VS Code has no per-extension or per-tab scrollbar API, so this necessarily colors scrollbars across the whole editor, not just Power Claude's own views — turn it off any time via Settings → Power Claude: 🎨 Branding & Theme.
• Non-destructive — your prior workbench.colorCustomizations values (or the absence of any) are snapshotted before the first apply and restored exactly on disable or uninstall.
• No reload needed — applies and reverts live.

---

⬆️⬇️ Chat scroll buttons — jump to the top or bottom of a long conversation

Small purple floating ↑ / ↓ buttons on the right edge of the Claude Code
chat thread: one click jumps straight to the beginning of the conversation,
one click jumps to the newest message — no hand-scrolling through a
thousand-line thread.

• One setting — powerClaude.chatScrollNav.enabled (default ON, Settings →
  Power Claude: 🧩 Claude Core).
• Only when useful — the buttons appear only while the thread is actually
  long enough to scroll; short chats stay clean.
• Smooth scrolling that respects your OS's reduced-motion preference, and
  survives Claude Code auto-updates via Power Claude's self-heal.

---

🧪 Detached Sessions (experimental · Pro) — your turn keeps running when you close the tab

Love that the Claude CLI keeps working when you refresh or close the window — but want a real graphical UI instead of a bare terminal? That's Detached Sessions.

Turn it on and a turn you launch runs inside its own systemd user service — its own cgroup, the same escape the rotation proxy relies on — so a browser-tab sleep, a page refresh, or closing the window can't kill it. When you come back, the dashboard reattaches and replays everything you missed, then live-tails the rest. The CLI's persistence, behind the GUI.

• Resilience — stop losing a 10-minute agent run to a flaky code-server / remote connection. It finishes whether or not you're watching.
• Efficiency — reconnect to the same running work instead of burning a fresh turn to rebuild context; you don't pay twice for the same thing.
• Safe by construction — default OFF; every turn still routes through the rotation proxy (quota & savings tracking intact); bounded by a hard turn-timeout, an idle reaper, and a concurrency cap; honours the pc emergency kill-switch.
• Requires Linux with a systemd --user manager (typical for code-server / remote dev). On other hosts the toggle stays disabled — it never pretends to persist when it can't.

Enable it from the dashboard's Rotation Safety Controls or the Setup & Optimize wizard.

---

Quickstart

Two install paths, both fully working from a single command.

VS Code Marketplace (recommended):

code --install-extension neural-llm.power-claude

Or search "Power Claude" in the VS Code Extensions panel. After install, click the Power Claude icon in the activity bar. The extension creates ~/.power-claude/ automatically, migrates any legacy data, and starts the local rotation proxy. No PATH changes required — every action is available from the dashboard and command palette.

npm CLI (terminal-only or scripting):

npm install -g power-claude
power-claude install

npm install -g puts two binaries on your PATH: power-claude (canonical) and pc (short alias). power-claude install creates ~/.power-claude/, deploys lib + hook scripts, and appends the bin path to your shell rc. Use pc help to see the full command list.

Commands at a glance:

pc list                       # all accounts with quota bars + status
pc status                     # proxy status dashboard
pc watch                      # LIVE TUI — account table + activity stream + modal hotkeys
pc rotate                     # rotate to next healthy account
pc rotate work-account        # rotate to specific account
pc health                     # probe accounts and render with live data
pc add                        # add an account profile
pc switch <name>              # switch active account
pc relogin <name>             # re-authenticate one account (OAuth flow)
pc save-profile <name>        # save current credentials as named profile
pc remove <name>              # delete a profile
pc export --output backup.json # export/back up all accounts to a file
pc import backup.json         # restore / move accounts onto another machine
pc logs -f --level error      # tail event log with filters
pc run                        # launch `claude` with auto-rotation
pc serve --port 8888          # start proxy server
pc doctor                     # full diagnostic checklist
pc config get|set|list        # CLI configuration
pc disable [--strip-profiles] # turn off rotation (destructive variant strips non-active)
pc enable                     # turn rotation back on

Both install paths use the same runtime directory (~/.power-claude/), so you can have the extension AND the CLI installed and they share state.

Add more accounts: click Link Account in the accounts tree (extension) or run pc relogin <name> (CLI) to walk through claude login for a new account profile. Multiple accounts enable rotation. See Pooling more accounts — one inbox, many logins for the fastest way to stand several up.

Move accounts to another workspace or computer: set everything up once, then carry the whole pool over instead of re-logging in everywhere. In the extension, use the Export / Import buttons on the Accounts panel; from a terminal, pc export --output accounts.json then pc import accounts.json on the other machine. The bundle contains your login credentials in plain text — keep it private, move it over a trusted channel, and delete it once imported (or use pc export --gpg <key> for an encrypted bundle). Accounts that already exist on the destination are skipped automatically.

Pooling more accounts — one inbox, many logins

Each Claude account is a separate Anthropic subscription with its own rate-limit windows — that independence is exactly what Power Claude pools. Every account you add is a real, paid subscription (Pool ≠ free capacity); the trick below is just how to manage many of them without juggling many inboxes. Every account stays within its own published limits — nothing here bypasses or circumvents Anthropic's terms.

You don't need a separate inbox per account. Sign each one up with its own email alias that all forward to a single inbox, then claude login each as a Power Claude profile:

How	What you do	Cost
Plus-addressing	[email protected], [email protected], … all land in [email protected] (Gmail, Fastmail, iCloud, most providers).	Free, instant — but some signup forms reject the +.
Custom-domain aliases / catch-all	Own a domain? Route [email protected], [email protected] (or a *@ catch-all) to your inbox. Cloudflare Email Routing is free; Google Workspace and Fastmail support it natively.	Free–cheap; most reliable for signups.
Alias service	SimpleLogin, addy.io, Apple Hide My Email, or Firefox Relay mint unlimited forwarding aliases on demand.	Free tiers cover plenty.
Separate real inboxes	Just use distinct real email addresses.	Free.

If you run your own mail server, a single admin command per alias is enough — e.g.:

# one alias per account, all forwarding to your real inbox
setup alias add [email protected] [email protected]
setup alias add [email protected] [email protected]
# …repeat, then `claude login` each at https://claude.ai and save it as a profile

Then add each in Power Claude (Link Account, or pc relogin <name>). Pro accounts on annual billing are the cheapest seats to pool — see Stop overpaying.

Enable the full resilience watchdog (optional, extension only): run "Power Claude: Install Session Lifecycle Hooks" from the command palette. Three lightweight hooks land in ~/.power-claude/hooks/lifecycle/ and emit heartbeat / session-end markers; the watchdog's precision detection depends on these. Opt-in; nothing in your Claude Code config is modified without explicit consent.

Enable editor gutter blame (optional): run "Power Claude: Install Timeline Hook" from the command palette to enable AI-edit annotations in VS Code's Timeline view and the editor gutter.

Pro features: enter your license key in Settings > Power Claude > License Key. A 7-day free trial starts automatically on install — no card required. See Free Trial vs Pro for what each tier includes.

---

Free Trial vs Pro

See neural-llm.com/pricing for current pricing and tier details.

Free to download and install. On first run Power Claude automatically starts a 7-day free trial — no card required, full Pro access for the window. After the trial, paid features (proxy, multi-account rotation, parallel dispatch, account pinning, the watchdog) lock and the extension runs in passthrough mode; only the read-only dashboard, profile management, and session resume remain. There is no ongoing free tier.

Pro unlocks unlimited accounts, the full watchdog with all four detection rules, the editor gutter blame annotations, the session graph view (Cytoscape.js force-directed and hierarchical layouts), pre-commit review, advanced search with field filters, and session history with no day limit.

Try Pro with founder pricing — the best value. Start a 14-day Premium Trial at neural-llm.com/pricing: card on file, $0 today, and your first charge isn't until day 15 — at the discounted founder rate you lock in for 2 full years. Cancel anytime before day 15 and you're never charged. Prefer no card at all? The 7-day free trial (no card) starts automatically on install.

---

FAQ

Does this work with the Anthropic API directly, or only with Claude Code?

Power Claude is built specifically for Claude Code — the CLI and IDE tool at claude.ai/code. It reads the local state Claude Code writes under its own config directory. It does not work with raw Anthropic API calls or with Claude.ai in the browser.

What data leaves my machine?

Only your license key, a hashed machine identifier, and the extension version are transmitted — to api.neural-llm.com during license validation. That validation is cached locally for 24 hours; no call is made on every keystroke. No prompts, no file contents, no transcripts, no usage data, no authentication tokens. Full details at neural-llm.com/privacy-policy.

Can I use multiple Claude accounts?

Yes. This is one of Power Claude's core capabilities. Add as many accounts as you have. Power Claude tracks health, cooldown state, and spend per account, and rotates automatically when the active account hits a rate limit. The Insight Graph annotates which account handled each part of a session.

Can I run several accounts from one email inbox?

Yes — you don't need a separate inbox per account. Sign each Claude account up with its own email alias (plus-addressing like [email protected], a custom-domain catch-all, or an alias service such as SimpleLogin / iCloud Hide My Email), all forwarding to one inbox, then add each as a Power Claude profile. Each account is still its own real, paid Anthropic subscription within its own limits — the alias is purely for managing many logins from one place. Step-by-step: Pooling more accounts — one inbox, many logins.

What happens when I hit a Claude rate limit?

If you have a second healthy account, Power Claude rotates to it automatically and resumes your session — usually within a few seconds. If all accounts are in cooldown, Power Claude displays the soonest-recovering countdown and optionally (powerClaude.autoSelectSoonest) activates the first account whose cooldown clears.

How is this different from GitLens?

GitLens maps your git history to your code. Power Claude maps your AI session history to your code. The two are complementary and designed to coexist. GitLens tells you which commit introduced a line. Power Claude tells you which Claude session wrote that commit, what it cost, which model it used, and whether it finished what it started.

How much does Pro cost?

See neural-llm.com/pricing for current pricing. A 7-day free trial (no card) starts automatically on install. The 14-day Premium Trial (card on file, $0 today, first charge on day 15, cancel anytime before then) locks in founder pricing for 2 years. There is no ongoing free tier — after the trial a paid subscription is required for Pro features.

What is the refund policy?

Full refund within 14 days of purchase, no questions asked. Contact [email protected] with your order details.

---

Extending Power Claude

Power Claude exposes a stable public API for other VS Code extensions to read session data, contribute custom tabs to the Session Detail webview, and enrich the Insight Graph with domain-specific data.

// In your extension's activate():
const powerClaude = vscode.extensions.getExtension("neural-llm.power-claude");
const api = await powerClaude.activate();   // PowerClaudePublicApi

// Read the live session index.
const sessions = api.sessions.list({ limit: 20 });
api.sessions.onDidChange(() => /* re-read */);

// Contribute a new tab to the Session Detail webview.
api.contributeSessionDetailTab({
  id:    "myExt.audit",
  label: "Audit",
  render(ctx) {
    return {
      html: `<p>Audit findings for ${ctx.sessionId}</p>`,
      messageHandlers: {
        "myExt.audit.openTrace": (payload) => /* … */,
      },
    };
  },
});

// Contribute a session enricher (lightweight read-only augmentation).
api.contributeSessionEnricher({
  id: "myExt.severityScore",
  label: "Severity Score",
  enrich(session) { return { score: 0.42 }; },
});

Full API surface at neural-llm.com/power-claude. Contracts under the PowerClaudePublicApi interface follow semver — breaking changes are rare and announced in the changelog.

---

What Power Claude does NOT do

• Does not make API calls to Anthropic on your behalf
• Does not bypass, circumvent, or violate any Anthropic rate limit or term of service — every account stays within its own published limits
• Does not transmit your prompts, code, transcripts, or authentication tokens off your machine
• Does not modify your global Claude Code config without explicit consent (all hook installers are opt-in command-palette invocations)
• Does not require any VS Code workspace to be open — the extension activates on Claude Code state changes regardless

---

What Power Claude writes to disk

Everything runtime lives under ~/.power-claude/:

Path	Contents
~/.power-claude/profiles/	OAuth profiles for each Claude account (rotation pool)
~/.power-claude/state/	Rotation state, lockouts, pending-recovery markers
~/.power-claude/logs/	events.jsonl, watchdog.log, rotation-audit.log
~/.power-claude/lib/	Bundled shell helpers, deployed at install time
~/.power-claude/hooks/	Lifecycle + rate-limit hook scripts
~/.power-claude/cache/	devtools-data.json, session-index.json
~/.power-claude/config/	config.json, auto-rewake-config.json

The only files Power Claude writes outside ~/.power-claude/:

File	Why
Claude Code's credentials file	Claude Code reads its OAuth credentials from here. Power Claude overwrites this file on rotation so Claude Code sees whichever account is active.
Claude Code's settings file	Hook registrations (with your consent). Power Claude appends entries; entries from other tools and your own settings are preserved. Removing the extension via "Power Claude: Uninstall Everything" strips every Power Claude entry cleanly.

Earlier versions stored profiles, state, and hook scripts under Claude Code's config directory. On first run, the migration module moves any legacy data into ~/.power-claude/ and deletes the legacy copies — no manual cleanup needed.

Complete uninstall: run "Power Claude: Uninstall Everything" from the command palette, or rm -rf ~/.power-claude && code --uninstall-extension neural-llm.power-claude. The uninstall command strips every Power Claude entry from Claude Code's settings file and removes ~/.power-claude/; your Claude Code credentials and other settings are untouched.

---

Privacy

Local-first. Power Claude reads from:

• ~/.power-claude/profiles/ — your rotation pool's OAuth profiles
• ~/.power-claude/state/ — rotation state, lockouts, recovery markers
• ~/.power-claude/logs/ — events.jsonl, rotation-audit.log
• Claude Code's own session transcripts — used only for token-bucket counts and session indexing (read-only)
• Claude Code's edit-history state — only if you opt in to Timeline tracking

The only files Power Claude writes outside ~/.power-claude/ are Claude Code's credentials file (so Claude Code picks up the rotated account) and Claude Code's settings file for hook registrations (with your consent). See What Power Claude writes to disk above for the complete list.

No data leaves your machine. No cloud telemetry. Full privacy policy at neural-llm.com/privacy-policy.

---

Get Power Claude

code --install-extension neural-llm.power-claude

Two ways to start, both $0 today: the 7-day free trial (no card, auto-starts on install), or the 14-day Premium Trial that locks in founder pricing for 2 years (card on file, nothing charged until day 15, cancel anytime). Start pooling your accounts today and watch the savings add up in your dashboard.

---

Support

• Bug reports: github.com/neural-llm-io/power-claude/issues
• Email: [email protected]
• Sales / licensing: [email protected]

---

License

Neural-LLM commercial EULA — see LICENSE and neural-llm.com/eula. Copyright (c) 2025-2026 Neural-LLM.

---

Trademarks

Claude and Claude Code are trademarks of Anthropic PBC. Visual Studio Code is a trademark of Microsoft Corporation. Cursor is a trademark of Anysphere Inc. Neural-LLM is not affiliated with, endorsed by, or sponsored by Anthropic, Microsoft, or Anysphere. Power Claude is an independent third-party tool that interoperates with the public file outputs of Claude Code.