Home Manage

Manage your GodotIQ license

Check your activation status, transfer between machines, or open a deep-link to the exact issue you're hitting. Everything here runs locally except the customer portal.

Quick actions

Pick your situation

Jump straight to the reason that matches what you're seeing.

Self-check

Run this one-liner to see your reported tier. Replace YOUR_KEY with the key Polar emailed you.

GODOTIQ_LICENSE_KEY="YOUR_KEY" godotiq auth status

Redact your key before sharing this output. The first few and last few chars are enough to identify it.

Reason codes

Deep-link with ?reason=<slug> to open the matching panel.

Pro tools not visible despite a valid key

Your key is set but `godotiq auth status` still shows tier community. Usually a config or restart issue.

  1. Fully restart your MCP client (close the app, don’t just reload the project).
  2. Confirm `GODOTIQ_LICENSE_KEY` is present in your client config and not accidentally quoted or truncated.
  3. Run `godotiq auth status` to check the reported tier.
  4. If still community, see /troubleshooting/#tier-community-despite-paid-license.
You’ve used all your activations

Your license has more active devices than the current soft cap allows. Free up a slot by deactivating a device you no longer use.

  1. Open your Polar customer portal from the purchase email.
  2. Deactivate a seat on a machine you no longer use.
  3. Restart your MCP client on the current machine.
  4. Run `godotiq auth status` again to confirm.
Your license key was revoked

The key has been invalidated, usually after a chargeback, refund, or manual revoke. Pro tools will not load until this is resolved.

  1. Email [email protected] with your order ID.
  2. Include redacted `godotiq auth status --json` output (remove your key).
  3. Wait for confirmation before re-adding the key.

Contact support

Reactivation required after a schema or key-format update

A product update expects a fresh activation handshake. This is a one-time local refresh, not a seat problem.

  1. Run `godotiq auth status --refresh` to force a new handshake.
  2. If instructed, remove the local Pro bundle cache and retry.
  3. Restart your MCP client and run `godotiq auth status` to confirm.
Pro bundle host unreachable or first run offline

First Pro activation needs to download the bundle from pro.godotiq.com once. Later runs work offline until the receipt expires.

  1. Check your internet connection and retry when online.
  2. Verify `https://pro.godotiq.com/health` is reachable from your machine (corporate firewalls may block it).
  3. Run `godotiq auth status` once the network is healthy.

This is a network / firewall issue, not a license problem.

System clock moved backwards

GodotIQ treats receipt timestamps as monotonic. If your system clock jumps back, receipts look invalid until you resync.

  1. Resync your system clock (macOS: `sudo sntp -sS time.apple.com`; Windows: Time settings → Sync now; Linux: `sudo timedatectl set-ntp true`).
  2. Restart your MCP client.
  3. Run `godotiq auth status` to confirm the tier is back to pro.
Corporate firewall blocking activation

Your network is blocking outbound HTTPS to Polar or pro.godotiq.com. This is a firewall issue, not a license problem.

  1. Ask your IT team to allowlist `api.polar.sh` and `pro.godotiq.com` over HTTPS.
  2. Retry `godotiq auth status` once the allowlist is active.
  3. If you cannot change network policy, email [email protected] about offline activation options.

This is a network / firewall issue, not a license problem.

Reason not listed? Collect diagnostics and email support

If `?reason=` is missing, unrecognized, or none of the panels above matches, gather a support report and we’ll take it from there.

  1. Run `godotiq auth status --json` and redact your license key before sharing.
  2. Note your OS + Python version, godotiq version, and MCP client.
  3. Email [email protected] with the redacted output and the exact error message.

Contact support

Transfer to a new machine

  1. Deactivate the old machine — either run godotiq auth deactivate locally, or email support if you no longer have access to that machine.
  2. Install GodotIQ on the new machine following the install guide at /getting-started/installation/.
  3. Add your license key to the new client's config (same env-var pattern as the install guide).
  4. Run godotiq auth status on the new machine to confirm activation. If you see an error, visit /troubleshooting/ or email [email protected].

Activate on any device. Free up a slot by deactivating another.

Can't access your customer portal?

Most users sign in at https://polar.sh/godotiq/portal with their purchase email. If that's not working, follow these steps instead.

Manage your license To manage your seats, update billing, or get a new license key: 1. Check your purchase email from Polar (subject: "Your godotiq purchase" or similar) → Contains your personal customer portal link 2. Can't find the email? → Check spam/promotions folder → Search "polar.sh" in your inbox → Email [email protected] with your purchase email address
What to include in your support email
  • Redacted godotiq auth status --json output (strip your license key).
  • Your OS (Windows / macOS / Linux) and Python version.
  • The AI client you're using (Claude Code, Codex, Cursor, Windsurf, VS Code).
  • The exact error message or symptom.
  • Your redacted config block (the snippet from the install guide).