Everything worth knowing before you install.

Search "Power Claude" in the VS Code Marketplace (or the Cursor extensions tab) and click Install. The 7-day trial activates the first time you open the extension panel — no account creation, no credit card, no license key paste. After install, every Pro feature is live for 7 days. When the trial ends, Pro features lock until you subscribe at $12/mo — the extension stays installed and your accounts stay configured.

You need at least one Claude.ai account that you own and pay for — Power Claude doesn't supply accounts. With a single account you still get the watchdog, Session Explorer, and analytics, but rotation has nothing to rotate to.

With 2+ accounts in Balanced Mode you get the headline benefit: 3 accounts in Balanced Mode = ~3x headroom on every rate-limit window — 5-hour, 7-day, tokens-per-minute, and requests-per-minute, independently. Hit a 429? Power Claude routes you to a healthy account in milliseconds, instead of sleeping the Retry-After window.

Yes. Rotation and the watchdog read and write shared files in ~/.claude/, so they operate on Claude Code sessions started in a terminal even when VS Code isn't in the foreground. The dashboard UI (Session Explorer, analytics panel, Session Trail, Pre-Commit Review) still requires VS Code or Cursor — that's where the rendering lives.

Run Power Claude: Uninstall Everything from the Command Palette to stop the proxy and delete all local data in ~/.power-claude/, then uninstall the extension from the Extensions panel. For every removal path — turning off individual hooks, a full local wipe, removing the CLI, and closing your account with our data-retention and erasure policy — see the uninstall guide.

One thing: a license-validation ping, cached for 24 hours. That request contains your license key and a VS Code machine identifier — nothing else. Power Claude never transmits your prompts, sessions, file contents, or account credentials. We have no API that ingests them; there is no endpoint to send them to.

Locally, in ~/.power-claude/ on your machine. Session Explorer reads from that directory and renders inside VS Code. Nothing is uploaded, mirrored, or synced to Neural-LLM. Delete the directory and the history is gone — Power Claude doesn't hold a backup copy.

No. We don't have API access to your Claude account. We don't proxy your prompts to our servers — Power Claude makes API calls from your machine, with your accounts, exactly the way Claude Code already does. There is no Neural-LLM-side log of what you typed, what Claude replied, or which files were touched.

Power Claude is an independent product developed by Neural-LLM. Not affiliated with, endorsed by, or sponsored by Anthropic, PBC.

Not to us. Power Claude has no server in the request path — it runs entirely inside your editor, reads your local Claude Code session files, and works with your own accounts. It never sees, stores, or transmits your prompts, your code, or your conversation. Your work goes exactly where it already went before you installed Power Claude — your own Claude Code session, under your own Anthropic account — and Power Claude adds no new destination. The only thing it ever sends us is an anonymous license check: a hashed key and a timestamp, nothing about your work.

Power Claude doesn't change your data path, so it doesn't change your obligations. Because it never receives your prompts or code and runs no servers in the request path, installing it adds nothing new for a security review to assess — the answer to "where does our code go?" is the same with Power Claude as without it. What your prompts and code are subject to once they reach Claude is governed by your own agreement with Anthropic, exactly as it is today; that part is between you and Anthropic and is outside Power Claude's scope. Power Claude is a local companion tool, not a compliance certification, and doesn't claim to be one.

Pro Monthly — $12/mo, cancel anytime. Pro Annual — $120/yr (save $24). Both unlock unlimited accounts, Balanced Mode, the session-resilience watchdog, Session Explorer, and per-account analytics. Every install starts with a 7-day free trial of Pro — no credit card required.

Unlimited accounts, Balanced Mode (parallel dispatch across every account you own), the session-resilience watchdog, Session Explorer, and live $/token analytics. The watchdog catches all four failure modes: process killed, OOM, network drop, mid-tool-call truncation — resume in one click. The analytics panel breaks down Pro, Max, and API spend by account and by model.

Yes, anytime. Monthly subscriptions cancel immediately and stop billing at the end of the current cycle. Annual subscriptions cancel at the end of the term — you keep Pro until the term expires, then no further charges. No cancellation fee, no email-the-team friction.

Nothing. Your Neural-LLM license is bound to your Neural-LLM account, not your Claude accounts. Add a Claude account, remove one, rotate all five for fresh ones — your Pro license keeps working. Power Claude just picks up whichever accounts you have configured the next time it runs.

No. Power Claude is a paid product with a free download and a 7-day free trial (full Pro access, no credit card required). After the trial, a paid Pro subscription is required to keep rotation, the watchdog, Session Explorer, and analytics. There is no permanent free tier. Your profiles and session data are never deleted — Pro features simply stay locked until you subscribe.

No. Power Claude is made by Neural-LLM, an independent software company. We have no affiliation with, endorsement from, or sponsorship by Anthropic, PBC.

"Power Claude" is an independent third-party product developed by Neural-LLM and is not affiliated with, endorsed by, sponsored by, or otherwise connected to Anthropic, PBC. "Claude" and "Claude Code" are trademarks of Anthropic, PBC, used here under nominative fair use solely to identify the Anthropic products with which our software interoperates.

Because that is the name of the Anthropic CLI product Power Claude works with. Our use is descriptive — it identifies the product we extend, the same way "for iPhone" identifies the platform a case is made for. We are not claiming ownership of, affiliation with, or endorsement by the "Claude" trademark.

We cannot speak for Anthropic. Power Claude operates within Anthropic's publicly available Claude Code CLI, reads local files that Claude Code writes, and installs lifecycle hooks in Claude Code's hook directory — all using documented, public interfaces. We use "Claude" and "Claude Code" descriptively under nominative fair use and display a non-affiliation disclaimer on every page and in the extension itself.

Power Claude works with your Claude Code accounts that you control and pay for. It does not scrape Anthropic's API, bypass authentication, circumvent rate limits through unauthorized means, or access any Anthropic systems directly. It reads local files on your machine and rotates between accounts you legitimately own.

That said, you are responsible for ensuring your use of Claude Code complies with Anthropic's current terms of service.

The canonical non-affiliation disclaimer and trademark acknowledgments are on the About page. The extension's LICENSE file and EULA contain the full legal text.

No. Power Claude reads your Claude Code session files locally on your machine and displays data inside VS Code. Your prompts, agent outputs, and session transcripts never leave your machine to Neural-LLM servers. The only network call Power Claude makes to our servers is license key validation — which sends your license key and VS Code machine ID, not any session content.

Claude Code exposes a Stop hook — a script that runs when Claude Code is about to exit. Power Claude installs a handler at that hook. When Claude Code hits a rate limit, the Stop hook fires, the handler detects the rate-limit signal in the exit state, and it rotates your active Claude account in ~/.claude/ to the next available account from your configured queue. Claude Code then resumes in the same session with the new account active. No context is lost because the session JSONL is uninterrupted.

Rotation only handles rate limits — events that cause Claude Code to exit via the Stop hook. The watchdog handles failure modes that don't produce a clean exit: process kills, OOM events, IDE crashes, network drops, and tool truncations. For these cases, the JSONL stops growing but no Stop hook fires. The watchdog detects the stall by polling lifecycle heartbeat markers and JSONL growth, then surfaces a recovery prompt.

Yes, in a limited and reversible way. Power Claude adds lifecycle hook scripts to ~/.claude/hooks/lifecycle/ and registers them in ~/.claude/settings.json. These hooks are installed with your explicit consent during setup and can be uninstalled at any time via the command palette (Power Claude: Uninstall Session Lifecycle Hooks). Power Claude also writes to ~/.claude/state/ for rotation state management. It does not modify the Claude Code binary or any Anthropic-owned files.

Yes, but with reduced capability. Without the lifecycle hooks, the watchdog falls back to coarser JSONL-idle detection — it can still detect stalled sessions, but loses heartbeat precision and final TodoWrite status. Rotation continues to work normally regardless of hook status; it uses the Claude Code Stop hook, which is separate from the lifecycle hooks.

The dashboard is the sidebar panel Power Claude shows in every workspace. Key tabs:

• Overview — Live account status, rotation handoff graph, per-account activity sparkline
• Routing — Smart vs Balanced mode, rotation kill switch, throttle-only mode
• Sessions — Every Claude Code session with status, model family, token totals, and one-click Resume / Stop
• Events — Real-time rotator/proxy event log with chip filters
• Analytics — Daily/weekly utilization per account and runout projections
• Settings — All ~/.power-claude/ knobs editable from the dashboard

Yes. Power Claude is a companion utility for your existing Claude Code accounts. It does not provide access to Claude or Anthropic's API. You must obtain, maintain, and pay for your own Anthropic Claude account(s) directly from Anthropic. Power Claude manages the accounts you provide — it does not supply accounts.

At minimum you need 1 account for basic watchdog and analytics (though with only 1 account, rotation has nothing to rotate to). Most users who want meaningful rate-limit resilience run 2 to 5 accounts. Pro and Team support unlimited accounts.

No. Power Claude manages accounts regardless of their Anthropic plan tier. If you mix account plans, the usage analytics dashboard will show you per-account spend and model availability separately. You can configure rotation priority to prefer accounts with more remaining capacity.

You can configure the same Claude account on multiple machines, but Power Claude manages accounts per-machine. License seats are also per-machine (one VS Code installation per seat). Using the same Claude account on two machines simultaneously may cause unexpected rotation behavior; we recommend keeping account assignments consistent per machine.

Users without an active paid license can file issues on the public GitHub repository. We monitor it and respond on a best-effort basis — typically within a few business days, but no SLA applies.

Pro subscribers get priority email support at support@neural-llm.com with a target response time of 1 business day. We aim to resolve most issues within 3 business days. Critical bugs that make Power Claude non-functional are treated as P1 and escalated.

Team subscribers get a dedicated support channel with a target response time of 4 business hours during our support hours: Mon–Fri, 9am–5pm Mountain Time. For urgent issues outside hours, email support@neural-llm.com and we will respond on the next business day. Critical issues affecting all team seats are treated as P1.

Power Claude requires VS Code 1.85.0 or later. We test against the current stable release and the two most recent stable releases. We do not officially support VS Code Insiders, but it generally works.

macOS: 12 Monterey and later (Apple Silicon and Intel)
Windows: Windows 10 and Windows 11, including VS Code running inside WSL2
Linux: Any distribution that can run VS Code and the Claude Code CLI

Power Claude works with any Claude Code version that writes JSONL session files to ~/.claude/projects/ and supports the Stop hook and PostToolUse hook in ~/.claude/settings.json. We test against the current Claude Code release. If Anthropic makes a breaking change to the hook system or JSONL format, we will ship a compatibility update as quickly as possible.

The VS Code extension itself only works inside VS Code. However, some features (rate-limit rotation, watchdog) can operate on Claude Code sessions started in a terminal outside VS Code, because they read and write shared files in ~/.claude/. Session Explorer and the VS Code dashboard require VS Code to be running.