Supercharge

Install

Install, pin a version, update, and put the binary on PATH

Install

The installer script is served from this site. It downloads the binary from the public GitHub release repo iotserver24/supercharge-releases.

macOS and Linux

Latest published release:

curl -fsSL https://superchargeai.in/install.sh | bash

Pin a version (the number is the release tag without v):

curl -fsSL https://superchargeai.in/install.sh | bash -s 1.3.20

Or:

SUPERCHARGE_VERSION=1.3.20 bash -c "$(curl -fsSL https://superchargeai.in/install.sh)"

1.3.20 is only an example of a published tag. Use the tag you want from the releases page. This docs set describes source 1.3.32.

Git Bash and MSYS2 on Windows can use the same bash script.

Windows PowerShell

irm https://superchargeai.in/install.ps1 | iex

A specific version:

& ([scriptblock]::Create((irm https://superchargeai.in/install.ps1))) -Version 1.3.20

Platforms

OSArchitectures
Linuxx86_64, aarch64
macOSx86_64 (Intel), aarch64 (Apple Silicon)
Windowsx86_64, aarch64

Asset names look like supercharge-linux-x86_64, supercharge-macos-aarch64, and supercharge-windows-x86_64.exe. On Apple Silicon, a Rosetta x86_64 shell still gets the arm64 build.

After install

supercharge --version
supercharge

sc is the same binary when the installer linked it and no other sc was already on PATH.

The bash installer adds ~/.local/bin (or SUPERCHARGE_BIN_DIR) to bash, zsh, or fish startup files inside a marked block, and it keeps a backup named *.supercharge.bak.*. A piped installer cannot change the parent shell's PATH. Open a new terminal, or run the export PATH=... line the installer prints. Set SUPERCHARGE_NO_MODIFY_PATH=1 on the installer side of the pipe when you manage PATH yourself:

curl -fsSL https://superchargeai.in/install.sh | SUPERCHARGE_NO_MODIFY_PATH=1 bash

The PowerShell installer adds %USERPROFILE%\.local\bin to the user PATH, including the current session.

Installer environment

VariableDefaultPurpose
SUPERCHARGE_VERSIONlatestPin X.Y.Z
SUPERCHARGE_GITHUB_REPOiotserver24/supercharge-releasesRelease repo the binary is downloaded from
SUPERCHARGE_BIN_DIR~/.local/binWhere supercharge is installed. No colons or newlines.
SUPERCHARGE_HOME~/.superchargeConfig and sessions
SUPERCHARGE_NO_MODIFY_PATH01 skips shell startup edits and extra PATH links

Update and build from source

Inside an installed CLI:

supercharge update

From a source checkout, with the pinned Rust toolchain:

cargo build --release -p supercharge-pager-bin

The binary is target/release/supercharge-pager. Put that file on PATH as supercharge. Upstream Grok installers install a different product.

Ctrl+I
Assistant

How can I help?

Ask me about configuration, installation, or specific features.