Exit codes and errors
For AI agents: this page is Markdown at https://squiggle.sh/docs/reference/errors.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.
What each squiggle exit code means, so a CI job can act on the number. Plus squiggle explain, which turns an exit code or an error code into the cause and a command that fixes it.
Exit codes
Every squiggle command exits with one of these codes. They don’t change between versions, and squiggle --schema-json lists them too.
| Code | Meaning |
|---|---|
0 | Success. There may be warnings. |
1 | The run failed: a flow, a suite, a gate or a diff. Also used for an unexpected error in Squiggle itself, which says what went wrong and where to report it. |
2 | A usage error, or a failure Squiggle expected, with a message that says what to do. |
3 | A licence is needed, has expired or is over its CI limit, or squiggle activate couldn’t get one (no key given, the key or trial was refused, or the licence server couldn’t be reached). squiggle license also exits 3 when nothing is active. |
4 | The --timeout you set ran out. |
5 | The device or the app on it isn’t usable: no device is available, another run is using it, or the app or its Squiggle agent didn’t start or answer. The error code says which. |
6 | Needs an agent: an agent: step had no recording that worked, and no agent was connected. No step failed. Pass --needs-agent fail to exit 1 instead. |
What CI should do with each
Codes 0, 1 and 6 are results: the flows ran. The others mean they couldn’t run properly, so fix the machine or the job before you trust the result. Pick what happened to see the code and what squiggle explain says about it:
Green.
squiggle explain 0exit 0 success (warnings allowed)Explain a code
Pass an exit code to squiggle explain, or an error code that comes with a fix. It prints what went wrong and the command that fixes it. It works without a licence.
squiggle explain 5squiggle explain E_STALE_DYLIBRun squiggle explain on its own to list the exit codes and the error codes it knows. For any other code, read its row below. Add --json to get the same thing as data.
Error codes
When a command stops on an error, the first line ends with the error’s code, even for a mistyped command or argument (E_USAGE). Under it come why it happened and the command that fixes it, where the error has them:
squiggle flow checkout✗ no flow at /Users/you/shop/.squiggle/flows/checkout.yaml E_NO_FLOW_FILE a name without .yaml resolves under the flows directory, such as auth/login for a flow in a folder; a file is used as given → squiggle flow with no argument, picks from the flows this project hasOnly an unexpected error in Squiggle itself has no code. Its first line says unexpected error: followed by the error’s type and message. Under it come the run id when there is one, the stack trace when the error has one, and where to report it, and the command exits 1. This is a bug in Squiggle, not in your app: send the output, together with what squiggle doctor prints, to the address it names.
| Code | What happened, and the fix |
|---|---|
E_NO_DEVICE | Nothing to drive was found (exit 5). For an iOS app, no simulator is booted: boot one with squiggle device simulator boot <udid> (squiggle device simulator list names every simulator and its UDID, and squiggle device simulator create makes one), or pass --udid to choose one. For a macOS app, the message says no booted app found: nothing named the app, so pass --udid mac:<bundle-id> or add "apps": { "macos": "<bundle-id>" } to .squiggle/config.jsonc, and Squiggle launches it when it isn’t running. For a React web app, it says no booted web app found: no URL is configured: run squiggle init, or add "apps": { "web": "http://localhost:5173" } to .squiggle/config.jsonc. |
E_DEVICE_BUSY | Another Squiggle run is driving this simulator (exit 5). The message names its process. Wait for it to finish, or stop it. If you know the two runs can’t collide, set SQUIGGLE_NO_DEVICE_LOCK=1. |
E_NO_HID | Squiggle couldn’t open its touch input on the simulator (exit 5). Run the flow again with --headless, which delivers taps inside the app instead, without gestures. |
E_DEVICE_AMBIGUOUS | Several simulators are booted, the command wasn’t told which one to drive, and neither your agent’s Squiggle server or Studio for this project, nor your running app, points at exactly one (exit 2). The message lists each one’s name and UDID, and which Squiggle session drives it. Pass --udid, or set SQUIGGLE_UDID or "udid" in .squiggle/config.local.jsonc. |
E_DEVICE_HELD | The command wasn’t told which simulator to drive, and every booted one runs an app another Squiggle session is driving: a CLI run or agent server of another project, or of another checkout of this repository (exit 2). Squiggle never takes that app. The message names each session, its project and port. Create a simulator of your own with squiggle device simulator create (or start a shut-down one with squiggle device simulator boot <udid>) and pass --udid (or set SQUIGGLE_UDID or "udid" in .squiggle/config.local.jsonc), or stop that session first. Naming the simulator doesn’t let a command relaunch that app: up, flow --fresh and the relaunch a run makes to replace an out-of-date agent stop with this error on it too. When the Mac is too busy for Squiggle to confirm who holds the app, the message says could not confirm who holds and names the check that didn’t answer: Squiggle neither takes nor relaunches an app it can’t tell is free, so run the command again once the Mac is less busy. Your agent’s tools refuse the same way (launch_app and run_flow with fresh included); your agent creates a simulator with the device tool’s simulator argument and picks it with the target tool. |
E_DEVICE | squiggle device couldn’t read or change a simulator setting (exit 5); the message says why. A permission change needs the app’s bundle id: name it, or declare the app in .squiggle/config.jsonc. text-size larger or smaller also stops with it when the simulator doesn’t report its text size: name the size instead, as in squiggle device text-size large. |
E_SIMCTL_TIMEOUT | A simulator command (xcrun simctl) didn’t answer in time and Squiggle stopped it (exit 5). The simulator’s services are stuck, often after an install that never finished. The message names the command, how long it waited, and the simulator when the command was for one: reboot that simulator with squiggle device simulator shutdown <udid> && squiggle device simulator boot <udid>, then run your command again. When the command that stopped was a boot (squiggle device simulator boot or create waits up to 10 minutes for one), the simulator may still be booting: check its state with squiggle device simulator list first, and reboot it only if it still isn’t Booted a few minutes later. When it names no simulator, quit Simulator and run xcrun simctl shutdown all. If that hangs too, run killall -9 com.apple.CoreSimulator.CoreSimulatorService. Your agent’s tools return the same message, with the reboot as the device tool’s simulator argument. |
E_UNSUPPORTED | The target has no such control (exit 2). Hardware buttons, appearance, contrast, text size, the status bar, location, permissions and the on-screen keyboard are iOS simulator settings, so squiggle device stops with this on a macOS app or a browser tab. |
E_NOT_INJECTED | The app is running without Squiggle’s agent (exit 5): its Squiggle SDK didn’t start the agent, or the agent failed to load. Run the flow again with --fresh, which relaunches the app with the agent; if it still doesn’t answer, reinstall Squiggle (npm install -g @squiggle.sh/cli). |
E_AGENT_SLOW | Squiggle launched your app with its agent, and the agent didn’t answer in time (exit 5). Squiggle waits up to 60 seconds when the agent has started inside the app or the Mac is heavily loaded, and the message gives the load average when it is. Nothing is wrong with the install: run again with --fresh once the Mac is less busy. Reinstall Squiggle only if the agent still doesn’t answer on an idle Mac. |
E_NO_APP | Squiggle couldn’t tell which app to launch (exit 2): nothing named one, or your flows name several. Add "apps": { "ios": "com.acme.shop" } to .squiggle/config.jsonc (squiggle init does it), or set SQUIGGLE_APP_ID=com.acme.shop for one run. |
E_NOT_AN_APP | squiggle init found no package.json in the folder (exit 2). Run it in your app’s folder, or pass the folder: squiggle init ./apps/shop. |
E_NOT_RN | squiggle init found no react-native, expo or react-dom dependency in the folder’s package.json, so there is no app to set up (exit 2). Run it in your app’s folder. |
E_INSTALL_FAILED | squiggle init couldn’t add Squiggle’s packages with your package manager (exit 2). The message prints the install command: run it yourself to see what the package manager objected to, then run squiggle init again. When a minimum release age setting held the package back, the message names the setting and how to let the package through, usually by adding it to the setting’s exclude list. |
E_KIT_INSTALL | squiggle init couldn’t write the agent kit into .claude/ (exit 2). The message names the paths and why. Make them writable, then run squiggle agent kit --install. |
E_LAUNCH_FAILED | Squiggle couldn’t launch the app (exit 2). On a simulator, it most likely isn’t installed there: build and install it once (npx expo run:ios or npx react-native run-ios). On a Mac, the app isn’t built yet, or is signed for release: build it in Debug. Then run again. When the message says the app quit right after it launched (exit 5), it most likely crashed while starting: squiggle perf crashes shows its crash report. Then run again with --fresh. |
E_NO_DYLIB | Squiggle’s agent, which ships beside the squiggle command, is missing (exit 2). Reinstall Squiggle (npm install -g @squiggle.sh/cli). |
E_STALE_DYLIB | The app is running an older copy of Squiggle’s agent than this build (exit 5). Quit the app, then run the flow again with --fresh. |
E_NO_HOST | The squiggle-host helper that drives the simulator wasn’t found (exit 5). Reinstall Squiggle, or run with --headless. On Linux there is no simulator: set device.provider (see Niteshift tasks), or drive a web app. |
E_BAD_URL | squiggle up --url, or web.url in .squiggle/config.jsonc, isn’t an address Squiggle can open (exit 2). Give a port (5173), a host and port (localhost:5173), or a full http:// or https:// URL. |
E_DEV_SERVER | Nothing answered at the web app’s address within 20 seconds (exit 5). Start your dev server with the command the message names, or the server for a production build, then run again. |
E_NO_BROWSER | No Chrome, Chromium or Edge was found, or not the one --browser, SQUIGGLE_CHROME or web.browser names (exit 5). Install one, or pass --browser with the path to one. |
E_BROWSER_LAUNCH | The browser exited or hung before Squiggle could connect to it (exit 5). The message ends with what the browser printed. Try another Chromium browser with --browser. |
E_NO_URL | squiggle up was given no address, and the project names no web app (exit 2). If the message says several dev servers answer, name the one to open: squiggle up --url 5173. If it says no dev server answers, start your dev server, then name its port. Or add "apps": { "web": "http://localhost:5173" } to .squiggle/config.jsonc. |
E_WEB_OPEN | Squiggle’s window for the web app didn’t open (exit 5). The message ends with the window’s last log lines and names the log file: read it with the cat command it prints. If it says this install has no squiggle CLI to hold the window, serve your agent’s tools with squiggle mcp. |
E_PRODUCTION_BUILD | The address squiggle up opened serves a production build, where component names are minified and React leaves out its development information (exit 2). Point it at your dev server, or pass --production to observe the production build anyway. |
E_CONNECT | The app never connected on the port the command was waiting on (exit 2). If the message says no app … connected … within 30 s, and this run does not relaunch it, the app isn’t running, often because it crashed, and the run (a bench, a run of several flows, or a report card) doesn’t relaunch it. Run the flow once on its own, or with --fresh. If it says … is showing the Expo dev-client launcher, and no Metro on :8081–:8090 or any port node or bun listens on serves it, start your app’s Metro (npx expo start), or name its server with metroUrl in .squiggle/config.jsonc. If it says … crashed while loading its JS, your app crashed before it connected: the message names where it crashed and the crash report to open. If it says the app’s bundle has no Squiggle SDK in it, or that Metro is up but slow to answer, see Troubleshooting. Otherwise, run squiggle doctor to check the app is set up and which port it connects to. |
E_TIMEOUT | The --timeout ran out (exit 4). Raise it, or give the command less to do. |
E_USAGE | The command line is wrong (exit 2): an unknown command, a missing argument, or a value the command doesn’t take. The message says which; squiggle <command> --help lists what the command takes. |
E_NO_FLOW_FILE | No flow file has that name or path (exit 2). A name without .yaml is looked up in .squiggle/flows, and a flow in a folder is named by its path there, such as auth/login. Run squiggle flow with no argument to pick from the flows the project has. |
E_NO_FLOW | squiggle bench was given no flow, or squiggle flow or squiggle watch was given none with no terminal to ask which (exit 2). Name it, as in squiggle flow checkout: each file in .squiggle/flows is a flow, named without .yaml, and the message prints the ls command that lists them. Your agent’s run_flow returns it for a name no saved flow has, before it waits for your app, with the closest names in closest, or the first names in library when none is close; there a flow in a folder is named by its path under .squiggle/flows, such as auth/login, and library_list shows every flow. |
E_FLOWS_DIR | squiggle flows found nothing to run (exit 2): with no argument, the project has no .squiggle/flows folder (squiggle init makes one); with an argument, no folder or flow has that name. The message lists the paths it tried. |
E_NO_PROGRAM_FILE | squiggle agent run found no program with that name or path (exit 2). A bare name is looked up in the flows and library folders. Run squiggle agent run with no argument to pick from the programs the project has. |
E_FLOWS_PER_SHARD_FLAG | squiggle flows was given --port, which it sets for each shard itself (exit 2). Leave it out, and name the first shard’s port with --base-port. |
E_FLOWS_UDID | squiggle flows was given --udid with no value, or a simulator named by --udid, SQUIGGLE_UDID or udid in your config isn’t booted (exit 2). For a simulator that isn’t booted, the message lists the booted ones: boot it with squiggle device simulator boot <udid>, or name a booted one. |
E_RELAY_SHARDED | squiggle flows was given --relay, which a sharded run can’t use (exit 2). Close Studio and run without --relay. |
E_NOT_INTERACTIVE | squiggle watch needs a terminal, since it runs until you stop it (exit 2). In CI or a script, use squiggle flow, which runs once and exits with a result. |
E_NO_LOGS | squiggle logs found no saved app data in this project (exit 2). Lines are saved while your agent’s Squiggle server, a flow run or Studio records an app the project owns: run a flow, as in squiggle flow checkout, then try again. With saved data but no line that matches, it says none match and exits 0. |
E_NO_RECORDING | squiggle flow --from-recording found no recording at that path (exit 2). Run squiggle replay to list the project’s recordings. |
E_RECORD_ARM | squiggle record couldn’t attach to the app (exit 2); the message says why. Run squiggle doctor to check the app is connected. |
E_NO_RUN | squiggle history rerun was given no run id, or one with nothing to rerun (exit 2). Run squiggle history to list the ids. |
E_BAD_PR | squiggle bench --pr needs a pull request number, such as --pr 123 (exit 2). |
E_FLOW_PARSE | The flow file isn’t valid YAML, or a step is malformed (exit 2). The message names the line and column. Quote any value that contains #. |
E_RUNS_WITH | squiggle flow was given a program whose runWith: names another command, such as squiggle agent branch (exit 2). Run it with the command the message prints. |
E_BAD_CHAOS | --chaos or --twin named a profile that doesn’t exist, or --twin none (exit 2). The profiles are slow, flaky, truncated and offline-midstep; --chaos also takes none, and --twin takes all. |
E_NO_STUBS | --stubs named a run that isn’t in .squiggle/runs, or one that made no requests (exit 2). Run the flow once with --capture-net, and pass the run id its footer prints. |
E_BAD_STUB_DELAYS | --stub-delays was given without --stubs, a pair wasn’t match=ms, or a match names no stubbed request (exit 2). The error lists the requests the stubs answer. |
E_BAD_RUN_COUNT | --fuzz-max, --race-max, --tune-reps or --repair-control wasn’t a whole number of runs, 1 or more (exit 2). |
E_TWIN_CLASH | --twin, --fuzz or --cache-twins was combined with a flag that also chooses the network or the starting state, such as --chaos, --stubs or --race (exit 2). Pass one of them. |
E_RACE_CLASH | --race was combined with --chaos or --stubs (exit 2). --race sets every request’s delay itself; drop the other flag. |
E_BAD_CLIFF | --cliff wasn’t VAR=lo..hi, such as N=10..800 (exit 2). |
E_BAD_TUNE_WEIGHTS | --tune-weights named a term other than dropped, blank or ms, or a weight that isn’t a number ≥ 0 (exit 2). |
E_TUNE_CLASH | --tune was combined with --fresh (exit 2). A relaunch puts each tunable back to its default; drop --fresh. |
E_APP_UNDECLARED | A command that saves what it finds (--twin, --fuzz, --race, --cliff, --tune, --repair, --cache-twins, --bisect-state, --matrix, --breakpoints-save, --confirm-jank, or squiggle store audit) ran in a project that names no app, or against an app the project doesn’t name (exit 2). Add "apps": { "ios": "your.bundle.id" } to .squiggle/config.jsonc (for a React web app, "web": "http://localhost:5173"), or set SQUIGGLE_APP_ID for one run. |
E_NO_PROJECT_STORE | A command would save into a folder that isn’t set up for Squiggle yet, so it saved nothing (exit 2). The message names the folder: run squiggle init there. squiggle agent validate with no files stops with it too when neither the folder nor its apps/* and packages/* holds a project, so there are no flows to check: name the flows, as in squiggle agent validate apps/mobile/.squiggle/flows, or run it in your app’s folder. |
E_APP_NOT_OWNED | squiggle crawl or squiggle card connected to an app this project doesn’t own, so it stopped instead of saving another project’s app here (exit 2). The message says which config key would add it, or run the command from the project the app belongs to. |
E_BISECT_STATE_CLASH | --bisect-state was combined with a flag that also chooses what each run starts from, such as --fresh, --cache-twins, --tune or --twin (exit 2). Pass one of them. |
E_MATRIX_PLATFORM | --matrix was run against a Mac app (exit 2). Its cells are simulator settings, so it needs an iOS simulator. |
E_CLOCK_UNSUPPORTED | squiggle flow --clock asked your app to move its clock and it couldn’t (exit 2). It needs a debug build of your app with the Squiggle SDK. |
E_BISECT_NATIVE | A commit in the squiggle bisect range changes native code or a dependency, which Metro can’t serve (exit 2). Bisect from after that commit with --good, or rebuild and bisect across it by hand. |
E_BISECT_USAGE | squiggle bisect got a range it can’t use: --good isn’t an ancestor of --bad, or the range is empty (exit 2). It also stops with it when it finds no app to serve the commits to: no app.json for a React Native app, or no Vite or Next.js app for a React web app. Pass --app-dir with the app’s folder. |
E_BAKEOFF_USAGE | squiggle bakeoff got an empty --against or a ref that isn’t a commit, or found no app.json (for a React web app, no Vite or Next.js app) (exit 2). Pass --app-dir when the app isn’t at the project root. |
E_BAKEOFF_NATIVE | A squiggle bakeoff branch differs from your checkout in native code or a dependency, which Metro can’t serve (exit 2). Compare branches that differ only in JavaScript. |
E_BAKEOFF_NO_RUN | squiggle bakeoff started the flow on a revision, but it never ran, for example because the app wasn’t running or the flow name is wrong (exit 1). The error above it says why; fix that and run again. |
E_CONTRACTS_PR | squiggle contracts propose --pr couldn’t commit, push or open the pull request; the message shows what git or gh said (exit 1). Run it with --write instead and commit the flows yourself. |
E_NO_INPUT | squiggle contracts propose found no passing agent run to learn from, or squiggle redact found nothing to redact (exit 2). Record a run first with squiggle agent run <program>. |
E_NO_AGENT | squiggle motion found no Squiggle agent in the app (exit 5). Rebuild the app with the current SDK, or relaunch it by running a flow with --fresh. In a Niteshift task, squiggle flow stops with it when the app’s agent didn’t connect: it prints the push command for the launch file; see Niteshift tasks. |
E_HANDOFF | In a Niteshift task, a step only the task’s agent can take, such as pushing Squiggle’s launch file or relaunching the app. squiggle flow --fresh stops with it before the first step (exit 2) and prints the step, and so does squiggle flow when the agent in your app connected but the SDK didn’t join within 30 seconds; an MCP tool returns it with the step in outsideTheApp. See Niteshift tasks. |
E_FLOWS_PROVIDER | squiggle flows runs a suite on this machine’s simulators, and in a Niteshift task there are none (exit 2). Run each flow with squiggle flow, or with your agent’s run_flow tool. |
E_AGENT_PORT_BUSY | In a Niteshift task, another Squiggle already listens on port 7780 for the app’s agent (exit 2). A task runs one at a time: use the one already running, usually your agent’s MCP server, or stop it first. |
E_MOTION_CAPTURE | squiggle motion couldn’t record the view around the tap, for example because the control to tap wasn’t on screen (exit 1). |
E_MOTION_MATCH | The file given to squiggle motion --match couldn’t be read (exit 2). It takes the output of an earlier squiggle motion --json. |
E_MOTION_VIDEO | squiggle motion --video couldn’t measure the recording (exit 2): the file is missing or isn’t a video, ffmpeg isn’t installed (the message gives the install command), --region doesn’t fit the frame, or --ignore covers all of it. With --against, the baseline must be an earlier recording or a report saved with --json. |
E_PROBE_RULE | A squiggle probe rule isn’t one (exit 2): it needs an input, a comparison and a number, such as render.max >= 30, and the input must be one that squiggle probe inputs lists. |
E_PROBE_UNSUPPORTED | The app doesn’t take probes (exit 5): it is a release build, which never runs one, or its Squiggle SDK is older than probes. On a React web app’s tab, probe anims, probe cell and --target ui stop with it too, since a browser has no worklet runtime. |
E_PROBE_REFUSED | The app refused the probe and said why (exit 2), for example a range wider than the input’s, more than 256 instructions in one probe, or more than eight probes at once. |
E_PROBE_NO_FIRINGS | squiggle probe export found no recorded firings for that id (exit 2). Run the probe with squiggle probe when first, with the same rules and --id. |
E_PROBE_MISMATCH | The rules given to squiggle probe export aren’t the ones the probe ran with (exit 2): re-running them over the recorded firings gives different answers. Pass the same rules, --any and --component as the probe used. |
E_PROBE_USAGE | A squiggle probe command is missing what it needs (exit 2): probe eval an expression, probe replay a flow name, probe when or probe export a rule, or --set a key=value pair. It also stops on more than 8 --component watches, or a --runner other than bun, vitest or jest. |
E_PROBE_EVAL_THREW | The expression you gave squiggle probe eval threw in your app (exit 1). The message is the exception your app’s runtime reported, such as a TypeError and where it was thrown: fix the expression, or read what it tells you about the app. |
E_NO_PROBE_TARGET | No JS runtime (or UI runtime, with --target ui) of your app is on the Metro port the probe read, or no Metro answers on that port at all (exit 5). Start your dev server, or run squiggle probe targets --port <port> to list what Metro reports, and pass --port for the right one. For a React web app, no browser tab is open on that address: open it with squiggle up --url, or run a flow. |
E_PROBE_AMBIGUOUS | Several devices run your app on the same Metro, so the probe can’t tell which to read (exit 2). The message lists them: pass --udid. |
E_JS_BUSY | Your app’s JS thread stayed busy for the whole 10-second wait, so the probe sent nothing (exit 2): connecting the debugger to running JS can crash the app. Run it again once the app is idle, for example after startup or once a JS animation loop stops. perf heap and perf profile wait the same way and report it as E_PERF. |
E_JS_UNOBSERVABLE | Squiggle couldn’t find your app’s process to check that its JS is idle, couldn’t tell which simulator runs it, or the app quit during the wait, so the probe sent nothing (exit 2). Pass --udid with the simulator the app runs on (mac:<bundle-id> for a macOS app), or set SQUIGGLE_UDID. perf heap and perf profile report the same case as E_PERF. |
E_NO_PROBE_PID | squiggle probe cpu has no process to measure (exit 2): pass --pid or --bundle-id, or set bundleId in .squiggle/config.jsonc. With a bundle id and no app running under it, it exits 5: launch the app first. |
E_PROBE_PID_GONE | squiggle probe cpu couldn’t read the process, usually because it quit (exit 5). Launch the app and run it again. |
E_PROBE_WOULD_PERTURB | A Squiggle run is driving the device, and probe timers or probe anims would disturb it (exit 5). Wait for the run to end, or pass --force when the run is your own. |
E_PROBE_RELOAD | probe reload, or probe anims before counting, couldn’t reload the app (exit 5). The message says why, for example that the app has no dev reload (a release build) or didn’t restart within 15 seconds. For probe anims, pass --no-reload to count anyway; the count can then include animations left over from earlier edits. |
E_PROBE_INCOMPLETE | probe timers didn’t finish inside the app (exit 5): the JS thread may be too busy to run its timers, which is itself worth a look. |
E_PROBE_REPLAY_REFUSED | probe replay couldn’t start (exit 5): Studio is focused on another device (the message gives the --udid to use, or choose the device under Devices in Studio), or the app refused the replay and the message says why. |
E_PROBE_REPLAY_TIMEOUT | probe replay didn’t finish in time (exit 5): the run may have stopped, or the JS thread is too busy. |
E_PERF | A squiggle perf command couldn’t do what you asked, and the message says why, for example a saved query that doesn’t exist (exit 2). squiggle perf --help lists the subcommands and what each reads. |
E_PRODUCT | A squiggle product command couldn’t do what you asked, and the message says why (exit 2). squiggle product --help lists the subcommands and what each reads. |
E_LICENSE_REQUIRED | No licence or trial on this Mac (exit 3). Run squiggle activate --trial, or activate a key. |
E_LICENSE_EXPIRED | The trial or licence has ended (exit 3). Run squiggle activate with a current key. |
E_CI_LIMIT | The licence server refused this CI token (exit 3): every CI place on the licence is in use, or the key is unknown, revoked or its subscription has ended. The message says which. A finished runner frees its place within 30 minutes; plans and their CI limits are on the pricing page. |
E_LICENSE_UNREACHABLE | Squiggle couldn’t reach the licence server (exit 3): from squiggle activate, or from a CI runner that hasn’t got a place in the last 24 hours. The message names the host: allow outbound HTTPS to it, then run the command again. |
E_NO_KEY | squiggle activate got no licence key (exit 3): nothing was piped in, no --key-file was given, and there is no terminal to ask on, or the --key-file couldn’t be read. Pass the key with --key-file <path>. |
E_ACTIVATION | The licence server refused the key (exit 3); the message says why. Check the key, or contact support with the output of squiggle license --json. |
E_TRIAL | The licence server refused the trial (exit 3); the message says why. A trial is recorded by the licence server, so a reinstall doesn’t start a new one. |
E_NO_LICENSE_SERVER | This copy of squiggle was built without a licence server, as a source checkout is, so there is nothing to activate (exit 2). Install a released build. |
E_CHECKSUM | squiggle update downloaded a binary that doesn’t match its published checksum, so it replaced nothing (exit 2). Run squiggle update again. |
E_NO_ARTIFACT | squiggle update found no build of the new release for this machine (exit 2): Squiggle is built for macOS on Apple Silicon and for Linux on x64 and arm64. squiggle bench stops with it when the flow run saved nothing to measure, with the run’s own exit code: run squiggle flow <name> to see why. |
E_UPDATE_SWAP | squiggle update couldn’t replace the squiggle binary, usually because this user can’t write where it is installed (exit 2). Run sudo squiggle update. |
E_UPDATE_UNVERIFIED | The binary squiggle update installed didn’t report the new version, so the previous one was put back and nothing is broken (exit 1). |
E_NO_RELEASE_ENDPOINT | This copy of squiggle was built without an update address, so squiggle update has nothing to update from (exit 2). Install a release build with npm i -g @squiggle.sh/cli@latest, or update it the way you installed it. |
E_UNKNOWN_CODE | squiggle explain was given an exit code or error code it doesn’t know (exit 2). Run squiggle explain to list the codes it knows, or find the code on this page. |
E_BAD_ACTION | squiggle telemetry was given an action it doesn’t take (exit 2). It takes on, off, status, flush or shown. |
For problems that don’t produce an error code, see Troubleshooting. For the messages about opening a web app, such as no Chrome, Chromium or Edge found, see React web apps.