License

Check status

License status belongs to paid threadgrid workflows, not free threadpoint project setup. The local status command reads THREADGRID_LICENSE_KEY. If the variable is not configured, it returns an unconfigured JSON status and does not contact the hosted entitlement service. When a key is configured, status validates it through the hosted entitlement service without requiring a Polar access token or repository secrets on the customer machine.

threadgrid license status
{
  "status": "unconfigured"
}

The current CLI ships license status, license refresh, andlicense activate. Status output includes shipped v0 capabilities only: archive indexing, record-only user-level memory consolidation, and ungated threadpoint-compatible project commands.

Activation

After checkout, use the license key from the Polar order email. The activation command validates the supplied key through the hosted entitlement service and writes a redacted receipt and verified local license state under local threadgrid state. Current status checks still read THREADGRID_LICENSE_KEY from the shell environment. Keep the real key in a local secret manager or environment variable, not in source files, support requests, or public issues.

export THREADGRID_LICENSE_KEY="..."
threadgrid license activate
threadgrid license status

Checkout

Use the limited-time early-adopter lifetime checkout package for v0 paid threadgrid access. The offer has no public end date yet. Checkout and order handling stay on the hosted buy surface; the local package maps to the threadgrid.lifetime entitlement for archive indexing and record-only user-level memory consolidation.

Customer portal

The license key is in the Polar order email. If that email is missing, open the customer portal, enter the license key you have locally, and use the Polar portal to view order and license details. The portal handoff validates the key before creating a short-lived Polar customer session.

V0 license state is bound to a local threadgrid device secret. Moving to a new machine is refresh-based: configure the same license key on the new machine and run activation or refresh there. Self-serve hosted device deactivation and device limits remain future work.

Safety

Paid personal, private, cross-project, archive, curation, recall, and support workflows should fail closed when license state cannot be verified. Public docs describe customer-visible behavior without exposing entitlement internals, secrets, or private customer data. Activation receipts store hosted status metadata and a license key fingerprint, not the raw key. Support-safe output is metadata-only by default and should not include license keys, customer IDs, order IDs, entitlement payloads, private paths, prompts, or local memory content.

Terms

Paid threadgrid product use is governed by the Threadgrid End User License Agreement. Threadpoint remains separately available under Apache-2.0.