Getting Started

Quickstart

Install the FORG agent, activate your license, and see your first signal in the dashboard — in under 5 minutes.


1. Install

Run the official installer script, which detects your platform and installs the correct forg binary to /usr/local/bin:

curl -fsSL https://forg.pro/install | sh

The installer builds with CGO enabled on macOS and Linux, giving you OS-native keychain integration (Keychain.app on macOS, libsecret on Linux, DPAPI on Windows). To opt into file-backed storage instead, set FORG_KEYSTORE=file:// before activating.

2. Activate

Copy your license key from forg.pro/dashboard SettingsLicense. License tokens use the format lic_<20hex>.

forg activate lic_a3f9e2c1b84d7f6e0a2c

# device fingerprint: a3f9e2c1b84d...
# Device name [mymac]:
#   ✓ Claude Code
#   ✓ Cursor
#
# FORG OS activated. 2 tool adapter(s) installed.
# forg: session started (a3f9e2c1)

Activation contacts forg.pro/agent/v1/activate, verifies the license, writes the identity bundle to your OS keychain, auto-detects installed AI tools, and immediately starts a monitoring session.

3. Start a session

forg activate starts a session automatically. For subsequent sessions, use forg on:

forg on
# forg: session started (a3f9e2c1)

# Optionally declare a goal:
forg on --goal "Build the auth flow"
# forg: session started (a3f9e2c1)
# forg: goal → Build the auth flow

See the Adapters guide for per-adapter setup details.

4. Verify

Run forg status to confirm your license is active and a session is running:

forg status

# user_id:        usr_a3f9e2c1b84d7f6e0a2c
# device:         a3f9e2c1b84d...
# engine:         https://engine.forg.pro
# license worker: https://api.forg.pro
#
# session:        a3f9e2c1 (active)
# goal:           Build the auth flow
#
# Installed adapters:
#   ✓ Claude Code (free)
#   ✓ Cursor (free)

5. Use your AI tool normally

Open Claude Code (or whichever adapter is installed) and start coding. FORG runs entirely in the background — you don't need to change your workflow.

When you're done, end the session and request a summary:

forg done

FORG never captures prompt text or completions — only metadata (model, tokens, cost, latency, session ID). Your code and conversations stay private.

6. View your data

Navigate to forg.pro/dashboard to see your sessions and signals in real time. Signals typically appear within 2–3 seconds of the tool call completing.

The dashboard shows:

  • Token and cost usage over time, with per-model breakdown
  • Active sessions and full session history
  • Rule triggers and anomaly alerts
  • Per-adapter and per-project attribution

Troubleshooting

forg: command not found

The installer puts forg in /usr/local/bin. Ensure that directory is on your PATH, or run `export PATH=/usr/local/bin:$PATH`.

Activation fails with 401

Check your license key format (lic_<20hex>). Copy the full token directly from the dashboard Settings → License page.

forg status shows no installed adapters

Install the AI tool first (Claude Code must be present), then run `forg connect claude-code` to wire the adapter manually.

No signals appearing in dashboard

Verify the hooks are written to ~/.claude/settings.json and that a session is active (forg status shows session ID).

forg: no active session after reboot

Sessions do not persist across reboots. Run `forg on` to start a new session.

© 2026 UpgradIQ, Inc.Edit this page on GitHub