Skip to main content

Power Claude — Downloads

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

19,039 downloads and counting

New Live count across every store — just getting started.

$2,148,551 estimated savings for users pooling Pro accounts instead of stacking Max plans how we estimate this

Available direct from this site since December 2025. Get Power Claude from your editor’s marketplace, from npm, or straight from GitHub Releases — or download the .vsix directly. Every release is archived as an immutable GitHub Release.

Choose how to install

Install Power Claude from your editor’s marketplace, from the command line, or with a direct download — every release also archived on GitHub. One-click installs auto-update; the rest are a single copy-paste.

Pick your editor

Tell us what you use — we’ll show the one simplest way to install Power Claude.

In VS Code, open Extensions, search "Power Claude" and click Install — the 7-day trial starts automatically, no card.

VS Code

Install in VS Code

One click — opens VS Code and installs the extension.

Cursor uses the same in-editor marketplace — search "Power Claude" in Extensions and click Install.

Cursor

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

Run the command, or install "Power Claude" from the Extensions panel (Open VSX).

Advanced — step by step
  1. Open the Extensions panel (Ctrl/Cmd + Shift + X).
  2. Search for "Power Claude".
  3. Click Install.
Windsurf uses the same in-editor marketplace — search "Power Claude" in Extensions and click Install.

Windsurf

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

Run the command, or install "Power Claude" from the Extensions panel (Open VSX).

Advanced — step by step
  1. Open the Extensions panel (Ctrl/Cmd + Shift + X).
  2. Search for "Power Claude".
  3. Click Install.
VSCodium installs from Open VSX — search "Power Claude" in Extensions and click Install.

VSCodium

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

Run the command, or install "Power Claude" from the Extensions panel (Open VSX).

Advanced — step by step
  1. Open the Extensions panel (Ctrl/Cmd + Shift + X).
  2. Search for "Power Claude".
  3. Click Install.
Browser VS Code / code-server — a one-step drop-in setup, nothing to install locally.

code-server / browser VS Code

Download the .vsix

Install "Power Claude" from the Extensions panel (Open VSX).

Advanced — step by step
  1. Open the Extensions panel (Ctrl/Cmd + Shift + X).
  2. Search for "Power Claude".
  3. Click Install.
New here? Watch the whole setup end to end — about thirty seconds.

No editor yet / Claude in the cloud

Get started →

One terminal line finds your editor (or none), downloads the latest build, verifies it, and installs it.

Or grab it from any download location:

VS Code Marketplace Easiest

VS Code · Cursor · Windsurf

One-click install with automatic updates.

Open VSX

Cursor · Gitpod · Theia

The open registry for VS Code-compatible editors.

npm

Terminal & CI · CLI-first

The same engine, installed globally from npm.

npm install -g power-claude

GitHub Releases

Every version · checksums

Immutable archive — changelogs and SHA-256 for every build.

Install from the command line

Prefer the terminal? Power Claude ships a standalone CLI too. This one line finds your editor (VS Code, Cursor, Windsurf…) — or runs headless for CI and servers — downloads the latest build, verifies its checksum, and installs it. No sudo, no account.

bash
curl -fsSL 'https://www.neural-llm.com/?option=com_neurallicense&task=download.vsix&file=install.sh' | bash
Prefer to read it first? View the script
#!/usr/bin/env bash
# Power Claude — one-line installer with a built-in dependency doctor.
#
# Downloads the latest Power Claude .vsix from neural-llm.com and installs it
# into your VS Code-compatible editor. Safe by design: HTTPS-only from the
# official origin, verifies the published SHA-256 when possible, validates the
# package, uses NO sudo, and makes no system changes beyond your editor's own
# extension directory. Before installing, it checks your environment and, when a
# dependency is missing or too old, either resolves what it safely can without
# sudo or prints the exact command for you to run. Inspect it first if you like:
#   curl -fsSL https://neural-llm.com/media/downloads/install.sh
set -euo pipefail

ORIGIN="${NEURAL_LLM_ORIGIN:-https://neural-llm.com}"
VSIX="power-claude-latest.vsix"
URL="${ORIGIN}/?option=com_neurallicense&task=download.vsix&file=${VSIX}"
MANIFEST_URL="${ORIGIN}/api/v1/power-claude/manifest.json"

say()  { printf '%s\n' "$*"; }
ok()   { printf '\033[32m✓ %s\033[0m\n' "$*"; }
warn() { printf '\033[33m⚠ %s\033[0m\n' "$*" >&2; }
die()  { printf '\033[31m✗ %s\033[0m\n' "$*" >&2; exit 1; }

# Compare dotted versions: `ver_ge A B` is true when A >= B (semver-ish, numeric).
ver_ge() { [ "$(printf '%s\n%s\n' "$2" "$1" | sort -V | head -n1)" = "$2" ]; }
# Lowest concrete version implied by an npm engines range (^1.106.0 → 1.106.0,
# >=20.0.0 → 20.0.0, 1.x → 1). Empty when the range carries no number.
range_floor() { printf '%s' "${1:-}" | grep -oE '[0-9]+(\.[0-9]+){0,2}' | head -n1; }
# First JSON string value for a key, from a flat object (no jq dependency).
json_str() { grep -oE "\"$2\"[[:space:]]*:[[:space:]]*\"[^\"]*\"" "$1" 2>/dev/null | head -n1 | sed -E 's/.*:[[:space:]]*"([^"]*)"/\1/'; }

# ── 1. Locate a VS Code-compatible CLI (no editor is launched — just its CLI). ──
CLI=""
for c in code cursor codium windsurf code-insiders; do
	if command -v "$c" >/dev/null 2>&1; then CLI="$c"; break; fi
done
[ -n "$CLI" ] || die "No VS Code-compatible CLI on your PATH (code / cursor / codium / windsurf). Enable your editor's shell command (Command Palette → 'Shell Command: Install code command in PATH'), then re-run."
say "→ Editor CLI: $CLI"

# Editor version (first token that looks like a version on the --version output).
EDITOR_VERSION="$("$CLI" --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -n1 || true)"
[ -n "$EDITOR_VERSION" ] && say "→ Editor version: $EDITOR_VERSION"

# ── 2. Download the latest .vsix to a private temp file (HTTPS forced). ─────────
TMP="$(mktemp "${TMPDIR:-/tmp}/power-claude-XXXXXX.vsix")" || die "Could not create a temp file."
PKG_JSON=""
trap 'rm -f "$TMP" "$PKG_JSON"' EXIT
say "↓ Downloading the latest Power Claude…"
curl -fSL --proto '=https' --tlsv1.2 "$URL" -o "$TMP" || die "Download failed from ${ORIGIN}."

# 2a. Sanity: non-empty + real .vsix (ZIP signature "PK").
[ -s "$TMP" ] || die "Downloaded file is empty."
case "$(head -c2 "$TMP")" in
	PK) ;;
	*) die "Downloaded file is not a valid .vsix package." ;;
esac

# 2b. Defense-in-depth: verify the published SHA-256 when a hashing tool exists.
SUMTOOL=()
if command -v sha256sum >/dev/null 2>&1; then
	SUMTOOL=(sha256sum)
elif command -v shasum >/dev/null 2>&1; then
	SUMTOOL=(shasum -a 256)
fi
if [ "${#SUMTOOL[@]}" -gt 0 ]; then
	EXPECTED="$(curl -fsSL --proto '=https' "$MANIFEST_URL" 2>/dev/null | tr ',' '\n' | grep -m1 '"vsix_sha256"' | grep -oE '[0-9a-f]{64}' || true)"
	if [ -n "$EXPECTED" ]; then
		ACTUAL="$("${SUMTOOL[@]}" "$TMP" | grep -oE '^[0-9a-f]{64}')"
		[ "$ACTUAL" = "$EXPECTED" ] || die "Checksum mismatch — refusing to install (expected ${EXPECTED}, got ${ACTUAL})."
		ok "SHA-256 verified."
	fi
fi

# ── 3. Dependency doctor — required deps block, feature-scoped deps only warn. ──
# Required engine versions are read FROM THE DOWNLOADED PACKAGE's package.json,
# so this can never drift from what the build actually requires.
if command -v unzip >/dev/null 2>&1; then
	PKG_JSON="$(mktemp "${TMPDIR:-/tmp}/pc-pkg-XXXXXX.json")" || PKG_JSON=""
	if [ -n "$PKG_JSON" ]; then
		unzip -p "$TMP" extension/package.json > "$PKG_JSON" 2>/dev/null || : > "$PKG_JSON"
	fi
fi

REQ_VSCODE=""; REQ_NODE=""; PKG_VERSION=""
if [ -n "$PKG_JSON" ] && [ -s "$PKG_JSON" ]; then
	REQ_VSCODE="$(range_floor "$(json_str "$PKG_JSON" vscode)")"
	REQ_NODE="$(range_floor "$(json_str "$PKG_JSON" node)")"
	PKG_VERSION="$(json_str "$PKG_JSON" version)"
fi

# 3a. REQUIRED: editor version must satisfy the extension's engines.vscode floor.
#     Catching it here turns the editor's cryptic "not compatible" install error
#     into a clear, actionable message — the #1 reason an install silently sticks
#     on an old build. Can't be auto-resolved without admin, so print the
#     fallback the user runs themselves rather than failing opaquely.
if [ -n "$REQ_VSCODE" ] && [ -n "$EDITOR_VERSION" ] && ! ver_ge "$EDITOR_VERSION" "$REQ_VSCODE"; then
	warn "Your editor is $EDITOR_VERSION but Power Claude ${PKG_VERSION:-(latest)} needs VS Code >= ${REQ_VSCODE}."
	say  "  Update your editor, then re-run this installer:"
	say  "    • VS Code:  Help → Check for Updates   (or: sudo apt-get update && sudo apt-get install --only-upgrade code)"
	say  "    • Cursor / VSCodium / Windsurf: update from the app, then re-run"
	say  "  Why this matters: installing into an older editor fails with a confusing"
	say  "  'not compatible' error and leaves you stuck on a previous version."
	die  "Editor too old for the current Power Claude build — update and re-run."
fi

# 3b. FEATURE-SCOPED: Node >= engines.node powers the `pc` CLI and the local
#     rotation proxy. The EXTENSION installs and runs without it, so a missing /
#     old Node only DEGRADES those features — warn, print the fallback, continue
#     (partial install), and nudge toward the full experience.
NODE_OK=1
NODE_VERSION="$(command -v node >/dev/null 2>&1 && node --version 2>/dev/null | grep -oE '[0-9]+(\.[0-9]+){0,2}' | head -n1 || true)"
if [ -n "$REQ_NODE" ]; then
	if [ -z "$NODE_VERSION" ]; then
		NODE_OK=0
		warn "Node.js (>= ${REQ_NODE}) was not found. The Power Claude extension will install fine; the 'pc' CLI and the local rotation proxy need Node."
	elif ! ver_ge "$NODE_VERSION" "$REQ_NODE"; then
		NODE_OK=0
		warn "Node.js $NODE_VERSION is older than the required ${REQ_NODE}. The extension installs; the 'pc' CLI / proxy need a newer Node."
	fi
	if [ "$NODE_OK" -eq 0 ]; then
		say "  Recommended (no sudo — per-user Node via nvm):"
		say "    curl -fsSL https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash && nvm install ${REQ_NODE%%.*}"
		say "  Or system-wide (needs sudo):"
		say "    sudo apt-get install -y nodejs        # Debian/Ubuntu"
		say "    brew install node                     # macOS"
		say "  Continuing — the extension's core features work now; install Node to enable the CLI + proxy."
	else
		ok "Node.js $NODE_VERSION satisfies the CLI/proxy requirement (>= ${REQ_NODE})."
	fi
fi

# ── 4. Install into the editor (extension dir only — no sudo, no system changes). ─
say "⇪ Installing into $CLI…"
"$CLI" --install-extension "$TMP" --force || die "Your editor reported an install error."

ok "Power Claude installed. Reload $CLI to activate it."
[ "$NODE_OK" -eq 0 ] && warn "Reminder: install Node.js to unlock the 'pc' CLI and the local rotation proxy."
exit 0

Version history

The complete release history of Power Claude. Only the current release is offered for download — retired versions are listed for reference and link to their changelog notes, but are no longer supported or installable from this site.

  1. v3.0.59 2026-07-02 deprecated — unsupported
  2. v3.0.56 2026-07-01 deprecated — unsupported
  3. v3.0.53 2026-07-01 deprecated — unsupported
  4. v3.0.52 2026-07-01 deprecated — unsupported
  5. v3.0.51 2026-07-01 deprecated — unsupported

← Back to Get Power Claude

Not sure it runs in your editor? Check the compatibility matrix — supported VS Code, Cursor, and Node versions, each proven by a real sandbox install.

Programmatic update checks call https://neural-llm.com/api/v1/power-claude/manifest.json — the CLI and the VS Code extension poll it on a 24h cadence and surface a non-blocking notice when a newer version is available.