Everything worth knowing before you install.

Install the host you bought from the VS Code Marketplace or Open VSX (or the Cursor extensions tab). Search Power Claude, Power Codex, Power Grok, or Power Kimi — not a bundle. Trial and checkout are per host; Power Claude documents its trial on the Power Claude page. After a trial ends, engine features lock until you subscribe. The extension stays installed and your host accounts stay configured.

You need at least one account you already own for that host. Power Agents do not supply Anthropic, OpenAI, xAI, or Moonshot seats. With a single account you still get watchdog, session tools, and analytics, but rotation has nothing to rotate to.

With 2+ accounts, failover has somewhere to go when a seat stalls. Claude-specific Balanced Mode math lives on Power Claude.

Yes for engine features that read host-local session files (watchdog, recovery). Those operate on host CLI sessions even when VS Code is in the background. The dashboard UI still needs VS Code or Cursor — that is where the panel renders. Claude Code path details: Power Claude.

Use the product Command Palette uninstall command to stop local services and delete that host's local state directory, then uninstall the extension. For every removal path — hooks, a full local wipe, CLI, and account erasure — 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 Agents never transmit your prompts, sessions, file contents, or host credentials. We have no API that ingests them.

Locally, in that product's state directory on your machine (Power Claude uses ~/.power-claude/). Session Explorer reads from disk and renders inside the editor. Nothing is uploaded to Neural-LLM. Delete the directory and the history is gone.

No. We do not have API access to your host accounts. We do not proxy your prompts. Calls leave your machine with your accounts, the same way the host CLI already works. There is no Neural-LLM-side log of what you typed or which files were touched.

Not to us. Power Agents run inside your editor, read local session files, and work with accounts you own. We never see, store, or transmit your prompts, your code, or your conversation. The only thing we receive is a license check: a hashed key and a timestamp.

Installing Power Agents does not add a new destination for prompts or code. The answer to "where does our code go?" is the same as without it: your host vendor, under your agreement with that vendor. We are a local companion, not a compliance certification.

Each host is its own product. Open pricing and pick Power Claude, Power Codex, Power Grok, or Power Kimi. Founder pricing starts at $12/mo per host (annual saves versus monthly). No forced bundle. Trial terms are per host — Power Claude's trial is documented on Power Claude.

Engine features on that host: multi-account failover where the host supports it, the session-resilience watchdog, session explorer, and spend analytics. Failure modes the watchdog covers: process killed, OOM, network drop, mid-tool-call truncation. Host-only extras (Claude Code profile rotation, host CLI hooks) stay on that product page.

Yes, anytime. Monthly subscriptions 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.

Nothing. Your Neural-LLM license is bound to your Neural-LLM account, not your host vendor logins. Add an account, remove one, replace them — the license keeps working. The product picks up whichever accounts you have configured the next time it runs.

No permanent free tier. Each host is paid, with a free download and a time-boxed trial where offered (Power Claude: see Power Claude). After the trial, a paid license is required for engine features. Profiles and session data are never deleted — features lock 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 Codex, Power Grok, and Power Kimi are the same company, same independence, for those hosts.

"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 Power Claude interoperates.

Because that is the name of the Anthropic CLI Power Claude works with. The use is descriptive — it identifies the host we extend. We are not claiming ownership of, affiliation with, or endorsement by the "Claude" trademark. Other family SKUs are named the same way for Codex, Grok, and Kimi.

We cannot speak for Anthropic. Power Claude operates against Claude Code's public local interfaces (session files, documented hooks). We use "Claude" and "Claude Code" descriptively under nominative fair use and display a non-affiliation disclaimer on every public page and in the extension. Codex / Grok / Kimi pages do the same for those hosts.

Power Claude works with Claude Code accounts that you control and pay for. It does not scrape Anthropic's API, bypass authentication, or access Anthropic systems except through the official CLI you already run. You are responsible for ensuring your use of Claude Code complies with Anthropic's current terms. Other hosts: you stay inside that vendor's terms for accounts you own.

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

No. Power Agents read host session files locally and display data inside the editor. Prompts, agent outputs, and transcripts never go to Neural-LLM servers. The only network call to us is license validation — license key and machine ID, not session content.

You configure a queue of accounts you already own for that host. When the active seat stalls, the engine fails over to the next healthy account so the job can continue. We never share or pool credentials across customers.

Power Claude's Claude Code path uses Claude Code's documented Stop hook and local ~/.claude/ state — details on Power Claude. Other hosts use that host's local state. Buy only the host you run.

Rotation handles clean seat-limit exits. The watchdog handles failure modes that do not produce a clean exit: process kills, OOM, IDE crashes, network drops, and tool truncations. It detects a stall by polling lifecycle heartbeats and session-file growth, then surfaces recovery instead of leaving you on a dead spinner.

Only with explicit consent, and only in reversible host-local files (hooks / settings the host already documents). Power Claude's Claude Code hooks install under ~/.claude/ and uninstall from the Command Palette. We do not modify host binaries. Other hosts: same rule, that host's state directory. See uninstall.

Yes, with reduced precision. Without hooks, the watchdog falls back to coarser session-file idle detection. Recovery still works; heartbeat precision drops. Claude-specific Stop-hook rotation notes are on Power Claude.

The sidebar panel every Power Agents host shows in the workspace. Typical tabs:

• Overview — live account status and activity
• Routing — failover mode and kill switch
• Sessions — host sessions with status, tokens, Resume / Stop
• Events — rotator / recovery log
• Analytics — utilization and spend on seats you already buy
• Settings — local knobs for that host

Claude-only chrome stays on Power Claude.

Yes. Power Agents are companion utilities for accounts you already own. We do not provide Claude, Codex, Grok, or Kimi access. You obtain and pay those vendors directly. We only manage the accounts you configure.

At minimum 1 for watchdog and analytics (with only 1 account, rotation has nowhere to go). Most people who want seat-limit resilience run 2 to 5 accounts on that host. Pro supports unlimited accounts per licensed host.

No. Mixed plan tiers are fine. Analytics show per-account spend separately. You can prefer accounts with more remaining capacity when the host supports that ranking.

You can configure the same vendor account on multiple machines, but Power Agents manage state per machine. License seats are per machine. Using the same vendor account on two machines at once can surprise failover; keep assignments consistent per machine.

Users without an active paid license can file issues on the public GitHub repository for that host. We monitor it 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 the licensed host non-functional are treated as P1.

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

VS Code 1.85.0 or later. We test against the current stable release and the two most recent stables. Insiders is not officially supported, but it generally works. Same floor for Cursor and other VS Code-compatible editors.

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 that host's CLI

Each SKU tracks the current public CLI for that host (session files + documented hooks). Power Claude tests against current Claude Code and the ~/.claude/ session/hook layout — see Power Claude. If a host vendor ships a breaking session format, we ship a compatibility update for that SKU.

The VS Code extension UI only runs inside VS Code (or a compatible editor). Engine features that read shared host-local files (watchdog, some failover) can still see CLI sessions started in a terminal. Session Explorer and the dashboard need the editor running.