Licence and trial

For AI agents: this page is Markdown at https://squiggle.sh/docs/licence.md. Every docs page is listed at https://squiggle.sh/llms.txt, and all of them are one file at https://squiggle.sh/llms-full.txt.

Start the trial, activate a key when you buy, and run Squiggle in CI. One activation covers Studio, the squiggle command and the MCP server on that Mac. CI runners never use a seat.

Start the trial

Terminal
squiggle activate --trial

The trial lasts 14 days, includes every feature and needs no card. You get one trial per Mac. A Linux machine is identified by its machine ID (/etc/machine-id), so machines cloned from one image with the same ID count as one.

Activate a licence key

When you buy, your licence key arrives by email. Run squiggle activate with nothing after it, and paste the key when it asks:

Terminal
squiggle activate

Don’t type the key after the command. It would stay in your shell history in plain text. In a script, pipe it in with squiggle activate -, or read it from a file with --key-file.

Activate from Studio

Without a licence, Home shows a notice and screens that need one are locked. Press Enter licence key (Renew licence on Home once a licence has lapsed), paste the key, and press Activate. A key that doesn’t work shows That key didn’t activate with the reason.

ButtonWhat it does
View plans, Plans and trial, RenewOpen the pricing page. Home says View plans; a locked screen says Plans and trial, or Renew when the licence has lapsed.
Re-checkReads the licence again, for example after you ran squiggle activate in the terminal.

Either way, the licence is saved in ~/.squiggle/license.json, and Studio, the squiggle command and the MCP server all use it.

Seats

Each Mac you activate uses one of your plan’s seats: 1 on Solo and 5 on Team. Activating the same Mac again uses the same seat. CI runners and cloud agent sandboxes never use a seat; see Run Squiggle in CI.

To move a seat to another Mac, free the old one in Polar’s customer portal under Licenses, then activate the new one. squiggle license --deactivate removes the licence from a Mac but leaves its seat claimed.

Check your licence

Terminal
squiggle license

It prints one of four states with the reason, the seats in use, and how long this Mac keeps working offline (for a trial, the day it ends). For a paid licence, that date is not when your subscription ends: it moves forward on its own while you’re online. Renewing your subscription keeps the same key.

StateWhat it means
entitledA paid licence is active on this Mac.
trialThe trial is running.
expiredThe trial or licence has ended, or this Mac was offline for more than seven days. Activate a current key to continue.
unlicensedNothing has been activated on this Mac, or the saved licence belongs to another machine.

Working offline

Squiggle checks the licence on your Mac, so it works offline. While you are online, a paid licence renews itself in the background when you run a squiggle command. Offline, it keeps working for up to seven days after it last renewed; squiggle license shows the days left. If it lapses, connect to the internet and run squiggle activate again.

When the trial or licence ends

Commands that need a licence stop and say why, with exit code 3. Your flows, recordings and data stay in your project. Sixteen commands keep working, including activate, license, explain and init, so you can always fix it from the terminal.

Run Squiggle in CI

A CI runner is a new machine on every build, so it doesn’t use an activation. Add your licence key to your CI as a secret named SQUIGGLE_LICENSE_TOKEN:

ci.yaml
env:  SQUIGGLE_LICENSE_TOKEN: ${{ secrets.SQUIGGLE_LICENSE_TOKEN }}

A CI runner never uses a seat, however many jobs you run, so CI can’t use up your Macs. Don’t run squiggle activate in the job: the token is all it needs, and with the token set, activate only takes the runner’s CI place, as any command does, and claims no seat. Your plan limits how many runners use Squiggle at the same time: 1 on Solo and 2 on Team. A runner over the limit stops with exit code 3 and says which limit it hit. A finished runner frees its place within 30 minutes.

A squiggle command keeps its place for as long as it runs, however long that is. Squiggle’s MCP server takes one place at its first tool call that needs a licence, or when your agent reads squiggle://license, and keeps it for the whole session; over the limit, its tools refuse with the same message. The same token works in a cloud coding agent’s sandbox, where each sandbox counts as one runner.

Squiggle tells runners apart by a random ID it keeps in ~/.squiggle/ci-slot, and sends only that ID and the token, nothing about the machine. Keep ~/.squiggle writable: otherwise every command counts as a new runner until its place expires.

Squiggle checks the licence with license.squiggle.sh over HTTPS, so allow outbound HTTPS to it wherever Squiggle runs. If a runner can’t reach it, for example because outbound access is restricted, a command that needs a licence prints this line:

Terminal
couldn't reach license.squiggle.sh (the licence server): allow outbound HTTPS to license.squiggle.sh in this environment

A runner that already got a place with the same token in the last 24 hours keeps running, so losing the connection partway through a job doesn’t fail it. A fresh runner, such as a hosted CI machine starting a new job, has no place yet: if its first command can’t reach the server, it stops with E_LICENSE_UNREACHABLE (exit code 3). The MCP server refuses its licensed tools the same way, and shows the line in its squiggle://license resource. squiggle activate always stops with E_LICENSE_UNREACHABLE when it can’t reach the server.

A Niteshift task is a new machine every time too. Add the same token to its secrets; see Niteshift tasks.