Install Forge

import { Tabs, TabItem, Aside } from ‘@astrojs/starlight/components’;

Forge is a single static binary with no runtime dependencies. Download it, put it on your PATH, and run forge --version. That’s the entire install.

Download

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/forge-macos-arm64 \
  -o forge
chmod +x forge
sudo mv forge /usr/local/bin/forge

Verify the download:

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/SHA256SUMS \
  | grep forge-macos-arm64 | sha256sum --check
# Expected: forge-macos-arm64: OK

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/forge-macos-x86_64 \
  -o forge
chmod +x forge
sudo mv forge /usr/local/bin/forge

Verify:

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/SHA256SUMS \
  | grep forge-macos-x86_64 | sha256sum --check
# Expected: forge-macos-x86_64: OK

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/forge-linux-x86_64 \
  -o forge
chmod +x forge
sudo mv forge /usr/local/bin/forge

Verify:

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/SHA256SUMS \
  | grep forge-linux-x86_64 | sha256sum --check
# Expected: forge-linux-x86_64: OK

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/forge-linux-arm64 \
  -o forge
chmod +x forge
sudo mv forge /usr/local/bin/forge

Verify:

curl -fsSL https://downloads.forge.ironpinelabs.com/releases/latest/SHA256SUMS \
  | grep forge-linux-arm64 | sha256sum --check
# Expected: forge-linux-arm64: OK

Download forge-windows-x86_64.exe from the releases page:

Invoke-WebRequest -Uri "https://downloads.forge.ironpinelabs.com/releases/latest/forge-windows-x86_64.exe" `
  -OutFile "forge.exe"

Move forge.exe to a directory on your PATH (for example, C:\Users\<you>\bin\).

Verify the SHA-256 hash:

# Download checksum file
Invoke-WebRequest -Uri "https://downloads.forge.ironpinelabs.com/releases/latest/SHA256SUMS" `
  -OutFile "SHA256SUMS.txt"

# Check — expected output shows OK
Get-Content SHA256SUMS.txt | Where-Object { $_ -match "forge-windows-x86_64.exe" }
Get-FileHash forge.exe -Algorithm SHA256
# Compare the two hashes manually

Invoke-WebRequest -Uri "https://downloads.forge.ironpinelabs.com/releases/latest/forge-windows-arm64.exe" `
  -OutFile "forge.exe"

Move forge.exe to a directory on your PATH. Verify as above using forge-windows-arm64.exe in the SHA256SUMS comparison.

Verify the install

forge --version

Expected output:

forge 1.4.0 (linux-x86_64)

The platform string (linux-x86_64, macos-arm64, etc.) confirms which binary you downloaded.

PATH setup (if needed)

If forge isn’t found after moving the binary:

Add to ~/.bashrc or ~/.zshrc:

export PATH="$HOME/.local/bin:$PATH"
# Move the binary there instead of /usr/local/bin if you prefer user-local installs

Then source ~/.bashrc or open a new shell.

Search for “Environment Variables” in the Start menu → “Edit system environment variables” → Environment Variables → System variables → Path → Edit → Add the directory containing forge.exe.

macOS Gatekeeper

On first run, macOS may block the binary with a “cannot be opened because it is from an unidentified developer” dialog.

Fix:

xattr -d com.apple.quarantine /usr/local/bin/forge

Or: System Settings → Privacy & Security → scroll down → “Allow Anyway” next to the Forge block.

Forge binaries are not yet notarized with Apple. This is on the roadmap. For now, the quarantine attribute removal is the standard workaround used by most developer tools distributed outside the Mac App Store.

Activate your license

If you have a license key (from a trial signup or purchase), activate it now:

forge activate <your-license-key>

Expected output:

forge: license activated (tier: solo, expires: 2027-04-17)
forge: machine fingerprint registered (1/1 slots used)
forge: all 21 MCP tools unlocked

No license key yet? Forge runs in Community Mode — 1 repo, 3 tools, CLI-only. You can still follow the rest of Getting Started. Run forge upgrade when you’re ready to start a 14-day free trial.

Next

Index your first repo — one command, and you have a structural model of your codebase.