# 0.6.1

Released 10 November 2026.

Fixes for 0.6.0. The npm CLI on a Mac loads its source parser again, a tap that a native alert handles is sent once, a step whose selector matches two controls fails instead of tapping one of them, and every part of Squiggle names a screen by its full route. Your editor's schema now gives every flow, program and config file the same verdict Squiggle does.

Some flows that loaded in 0.6.0 now stop with a parse error that names the mistake, instead of running a step that proves nothing: a value of the wrong kind (such as `optional: yes`, `nth: "2"`, or a `waitFor` condition that isn't true or false), a misspelt key in a nested selector, an unknown or empty predicate (`droppedFrames: { le: 2 }`, `droppedFrames: {}`), and `launchApp: com.acme.shop` (write `launchApp: { app: com.acme.shop }`). A step whose selector matches two controls now fails and lists them: add `nth` or a second field. A `udid` in your config now limits `squiggle flows` to that simulator. Name screens by their full route, as `status` shows it (`(tabs)/index`); an older name in a navigation contract still checks, with a warning naming the route to write.

## CLI

- **New**: `squiggle agent validate` checks the flows and intent programs you name (files, folders or globs) without a device or a licence, prints one line per file, and exits 1 if any fails; `--parse-only` checks only that each one loads
- **New**: `squiggle flows --udid` runs a suite only on the simulators you name; `udid` in your config or `SQUIGGLE_UDID` names one too
- **New**: `shards` in `.squiggle/config.jsonc`, or in a profile, sets how many simulators `squiggle flows` uses; `--shards` still wins
- **New**: `squiggle logs --since` takes a duration, such as `2m`
- **Fix**: the npm CLI on a Mac loads its source parser again, so `agent validate`, `legibility --fix` and `affected_by_diff` work: every file in the package is now signed by the same team as `squiggle`
- **Fix**: `squiggle flow` on an app another Squiggle holds names that Squiggle and moves the app to its own port, instead of waiting for a connection that never came
- **Fix**: `squiggle update` and `squiggle uninstall` run from Studio's command say to update or remove Studio, and an npm install is told the npm command; `squiggle doctor`'s advice matches how you installed
- **Fix**: `squiggle init` leaves an existing Squiggle server entry alone under any name, including one Claude Code reads from a parent folder or `~/.claude.json`
- **Fix**: `squiggle device permission` opens the app again when iOS closes it to apply the change
- **Fix**: `squiggle motion` follows a view the tap brings in, such as a sheet

## Agents & MCP

- **Fix**: `run_flow` uses the flow's own `config: { autoScroll }`; an `autoScroll` you pass still wins
- **Fix**: a worktree app's `run_flow` recording is saved in the worktree that owns it, and a refused recording names that project
- **Fix**: the production rule lets a run remove what it created itself, such as a prompt it typed, and its refusal says what would lift it
- **Fix**: the `device` tool opens the app again when iOS closes it to apply a permission change, and says so with `relaunched`
- **Fix**: a live `motion` track follows a view the tap brings in, instead of refusing it
- **Fix**: `motion` names a part swinging in place, such as a spinner, instead of calling it jank; a long wait mid-recording is a pause, not a stall; and a filmstrip gives a recording's real frame rate
- **Fix**: a run that loses the app names the other Squiggle attached to it, and so does a `wait_for` the app never came back to

## Flows & device

- **New**: a `device:` step takes the MCP device tool's call (`hideKeyboard`, `showKeyboard`, `location` or `permission`) and runs as the step that does it; the tool's other settings stop the flow with the command to use instead
- **Fix**: a tap that closed a native alert, opened a search field or moved a control iOS draws is no longer sent a second time; the step's warning says why it wasn't
- **Fix**: a step whose selector matches two controls fails and lists them, instead of tapping one; a component that draws no view no longer competes with the control it wraps, and a step that can only reach one fails with "the target draws no view to tap"
- **Fix**: a swipe on a control waits for the screen to settle, so a swipe down right after a sheet opens closes it
- **Fix**: an in-app browser's Done button is listed and tappable, and an iOS 26 toolbar search field is listed by its placeholder
- **Fix**: every part of Squiggle names a screen by its full route, so a contract, budget or program written from `status` is checked instead of coming back never recorded; an older name still resolves to the route it meant
- **Fix**: `assert: { store: … }` compares a value with true, false or text, and `store: { useCart: {} }` checks that the store exists
- **Fix**: your editor flags exactly the flows, programs and config Squiggle refuses, and fetches the current schema instead of keeping its first copy
- **Fix**: the agent no longer crashes an app while Squiggle stops it, which showed up as a crash report for a run that passed
