Riggr

Install and sign in

Download the installer, open the app, sign in.

Install and sign in

Payment cleared — let's open the app for the first time.

Download the installer

Right after payment the site shows a thank-you page with a Download button. It detects your OS and serves the right installer. You can also download later from your account dashboard at getriggr.app.

The download endpoint requires an active site session — keep the browser logged in.

Install

  • macOS — open the .dmg, drag Riggr into Applications.
  • Windows — run the .exe, follow the installer.
  • Linux — AppImage or .deb, run/install as you'd expect.

If the OS complains about an "unverified developer", approve it. The binary is signed, but Microsoft / Apple still want a first-time confirmation.

First sign-in in the app

When Riggr first opens, it asks you to sign in with the same account you used to buy the license (Google or GitHub). The flow follows the OAuth device-code pattern:

  1. Open Riggr.
  2. Click Sign in.
  3. The app opens getriggr.app in the browser with a short code pre-filled.
  4. You approve in the browser, the app detects it and continues on its own.

If the browser doesn't bounce back to the app, the welcome screen has a manual field to paste the code.

What happens when you sign in

  • Riggr saves a JWT into <userData>/riggr-license.json, encrypted with Electron's safeStorage (DPAPI on Windows, Keychain on macOS, libsecret on Linux).
  • It generates a unique device fingerprint (UUID + hash of hostname/username/platform) and stores it in riggr-device.json. That fingerprint goes on every license request — if the token leaks and gets used on another machine, the server refuses.
  • Every hour online, the app re-validates the license by calling /api/entitlement. Offline, it keeps working for up to 72 hours with the cached result. Past that, it needs connectivity to re-check.

Settings worth tweaking now

Before building workspaces, open Settings (gear icon in the title bar or Ctrl+Shift+P → Settings).

  • CLI agent — the Agent Terminal runs the CLI (Claude Code, Codex, or Gemini) inside a pseudo-terminal. Login is handled by the CLI itself, not by Riggr — you don't paste an Anthropic, OpenAI, or Google key. On first run the CLI prints the auth link and opens your browser.
  • API Keys (optional) — only for credentials to external tools you want available to the agent: a GitHub token for an MCP, Docker Hub for private images, and so on. Riggr never asks for an AI provider key.
  • Language — pt-BR or en-US.
  • Theme — dark, dimmed, oled, or white.
  • Agent → Default CLI agent — which binary the Agent Terminal uses: claude-code (default), codex, gemini, or a custom path.
  • MCP — optional, but very useful. See MCP servers.

All set. Next page: Your first workspace.