# 0.6.3

Released 11 November 2026.

Fixes for 0.6.2. A native alert's button is tapped by its label, a button in the navigation bar presses, `back` waits for iOS 26's swipe-back to finish, and a monorepo works from its repository root: `agent validate` there checks your app's flows. Your agent stays on the simulator it attached to, and a crash while your app loads is named as one.

Some behaviour changed. An MCP session no longer moves to the newest app on your Mac: it stays on the simulator it attached to until your agent calls `target` or `launch_app` with your app, so after `squiggle up` for another device, switch with `target`. In a flow step, `role:` beside `label:` now narrows the label instead of turning it into the step's name, so `{ label: Sign out, role: AXButton }` taps the button labelled Sign out. MCP `tap` answers `ok: false` for a tap on your app's control that does nothing, as flows already did. A `point` string Squiggle can't read is refused before the flow runs. In a monorepo, an app without its own `.squiggle` folder no longer takes `"release": true` from another app's config.

## Desktop app

- **Fix**: an app in a monorepo is named after its repository, and its icon is found in an `app.config.ts` too
- **Fix**: the device header's Inspecting label no longer runs over the screen name

## CLI

- **Fix**: in a monorepo, `squiggle agent validate` from the repository root checks each flow against the project that holds it, and fails with `E_NO_PROJECT_STORE` when it finds no project, instead of passing with 0 flows. `agent validate --hook` checks only the file your agent just edited, for the agent kit's flow-edit hook
- **Fix**: in a monorepo whose root has no `.squiggle` folder, commands run at the root (or in a shared package) use the one app under `apps/` or `packages/` that has one; with two such apps, run them in the app's folder. `squiggle init` at the root sets up that app
- **Fix**: the testID check in `agent validate`, `affected_by_diff`, `crawl --changed`, `find` and `legibility --fix` also read your shared packages' `src`, `app` and `components` folders
- **Fix**: when your app crashes while loading its JavaScript, the run says so and names the crash report, instead of "reloaded its JS … did not connect again"
- **Fix**: Squiggle no longer opens your app's link over the dev client while it is still loading from a slow Metro, which loaded your JavaScript twice
- **Fix**: "JS never connected" is printed only when your app really doesn't connect, not on a run that connects a few seconds later
- **Fix**: an unexpected error prints its type, message, run id and stack, and a command that fails without an error exits 1 instead of 0
- **Fix**: `squiggle probe reload` reloads only your app, waits until it has restarted, and exits 5 with `E_PROBE_RELOAD` if it doesn't; `probe eval` reports an expression that throws as `E_PROBE_EVAL_THREW`, and a probe with no Metro on its port says so and exits 5
- **Fix**: `squiggle doctor` lists your project's own port first and marks ports other Squiggle sessions hold
- **Fix**: navigation contracts read a screen recorded without its route group (`tasks/index`) as its full route (`(app)/tasks/index`); an inconclusive answer names the screens holding it open
- **Fix**: `motion --video`, the `filmstrip` tool and its `luma` window report a recording's frame rate the same way, and a `luma` window starts with the frame already on screen and says when the screen held still

## Agents & MCP

- **Fix**: your agent stays on the simulator it attached to; only `target`, `launch_app` with your app, or that simulator shutting down moves it, and a move is named in `status.target.movedFrom` and in the next tool result. Every tool uses that one device
- **Fix**: `tap` answers `ok: false` with "the tap did nothing" when your app's control doesn't react, with or without `expectRoute`
- **Fix**: `batch` takes `device` steps
- **Fix**: `inspect` and `renders` on a control with no React component behind it (a navigation bar button) say so, instead of "matches more than one element"
- **Fix**: `status` stops listing a CLI run whose process was killed

## Flows & device

- **Fix**: with a React Native `Alert` up, a selector resolves to the alert's button, never to a control of your app the alert covers that shares its label; `describe`, `find` and `tap` agree
- **Fix**: `role:` beside `label:` narrows the label: `{ label: Sign out, role: AXButton }` matches the button labelled Sign out instead of every button
- **Fix**: a tap on a button in the navigation bar (a `headerLeft` view) presses it; a tap now holds still the way a finger does
- **Fix**: `back` waits for a swipe-back's transition to finish, up to 5 seconds, before it judges whether the screen changed
- **Fix**: a `point` accepts `"120, 640"`, percentages up to `100%` and `[x, y]` fractions, and refuses anything else with the forms it takes, instead of failing as "selector did not resolve"
- **Fix**: `find` and `tap` reach the items of Expo's developer menu, so `tap: { text: Reload }` works

## SDK

- **Fix**: in a monorepo, an app without its own `.squiggle` folder keeps Squiggle out of its release build unless the repository root's config opts in; another app's `"release": true` no longer applies to it
