# 0.6.7

Released 13 November 2026.

Fixes for 0.6.6. Two projects on the same port no longer lock each other out: another project's Squiggle that only accepted your app's connection lets your session take it, and a CLI run on another simulator never holds your app. Startup profiles from your agent name your own files and give a real duration. You can create, boot and shut down a simulator from the CLI and your agent, and `squiggle init` can make one for your project. Selectors can check what a text says by pattern or number. Squiggle's own hold on the JS thread at launch no longer counts against your app, and the report card stops flagging memoized providers, a nested stack's `index` and read-only text.

Some behaviour changed. A `testID` alone no longer makes an element a control: the legibility checks (hit target, role, contrast) apply to elements that take touches, have an interactive role or an agent hint. A `udid` belongs in `.squiggle/config.local.jsonc`, which every surface reads and a running session picks up when it changes. `squiggle init` without a terminal now reads the simulator list to tell you when none is free. `doctor` warns when another project's Squiggle holds your port instead of calling it yours.

## Agents & MCP

- **Fix**: `intent_wait` streams each step as progress again
- **Fix**: an error during another incident's recording reaches your agent by name

## Performance

- **Fix**: your agent's startup profile names files in your own project, not another project running on the same Mac, and its duration is the real window
- **Fix**: every launch in a run keeps its own startup profile, including a flow's `launchApp` and a relaunch to heal a stale agent
- **Fix**: `run_flow` keeps the first screen's slow `useEffect` spans
- **Fix**: Squiggle's hold on the JS thread at launch is no longer reported as your app's long task, startup time or slowdown
- **Fix**: an app whose startup keeps JavaScript busy no longer sits out a 2 s hold Squiggle asked for too late

## Everything else

- **New**: `squiggle device simulator list|create|boot|shutdown` and your agent's `device { simulator }` make and manage simulators; a shutdown refuses a simulator Studio, an agent or a CLI run is driving
- **New**: offers a simulator of your project's own and records its udid in `.squiggle/config.local.jsonc`; `--create-simulator` does it without asking
- **New**: `textMatches` checks a node's text against a pattern and `textNumber` compares the number in it (`{ gt: 0 }`), in flows, `assert` and every tool that takes a selector
- **Fix**: another project's Squiggle that only accepted your app's connection, and isn't driving it, no longer locks your project out: your run takes the app over
- **Fix**: a CLI run on another simulator never holds your app, and with no other Squiggle running the app is free at once
- **Fix**: a running MCP server follows edits to `.squiggle/config.jsonc` and `config.local.jsonc`, so `launch_app` starts the app and simulator the files name now
- **Fix**: each screen's interface is checked against its own testIDs, so a nested stack's `index` no longer fails Home's
- **Fix**: the recreated-context rule names the fields that changed and no longer flags memoized providers or values that change with real navigation
- **Fix**: read-only text and an input that isn't editable or takes no touches are no longer counted as controls
- **Fix**: a tap that changed nothing says its effect may be off React (a worklet or native state) and how to make it visible to an assertion
- **Fix**: a simulator command that hangs stops with `E_SIMCTL_TIMEOUT` and says how to recover, including create, boot and shutdown
- **Fix**: a new simulator's first flow is no longer covered by Expo's developer menu
- **Fix**: every hint to boot a simulator names `squiggle device simulator boot`
- **Fix**: `squiggle init` installs the SDK at the CLI's own version, names a Bun or pnpm release-age setting that blocks it, and picks the right Nitro version for a `catalog:` React Native
- **Fix**: a failed `init` marks each change done, failed or not applied, instead of showing every planned change as done
- **Fix**: `squiggle doctor --quick` reports the device, the app, a version mismatch between the SDK and the CLI (also when the SDK is installed in an app folder of a monorepo) and the next step in about a second, without a licence
- **Fix**: the agent kit's session hook shows what `doctor --quick` found, its simulator guard blocks only a command that erases or deletes a simulator, and `agent kit --install` says when the MCP server isn't registered yet
