ChangelogShared ports, simulators of your own and startup holds
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_waitstreams each step as progress again - Fixan error during another incident's recording reaches your agent by name
Performance
- Fixyour 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
- Fixevery launch in a run keeps its own startup profile, including a flow's
launchAppand a relaunch to heal a stale agent - Fix
run_flowkeeps the first screen's slowuseEffectspans - FixSquiggle's hold on the JS thread at launch is no longer reported as your app's long task, startup time or slowdown
- Fixan 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|shutdownand your agent'sdevice { simulator }make and manage simulators; a shutdown refuses a simulator Studio, an agent or a CLI run is driving - Newoffers a simulator of your project's own and records its udid in
.squiggle/config.local.jsonc;--create-simulatordoes it without asking - New
textMatcheschecks a node's text against a pattern andtextNumbercompares the number in it ({ gt: 0 }), in flows,assertand every tool that takes a selector - Fixanother 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
- Fixa CLI run on another simulator never holds your app, and with no other Squiggle running the app is free at once
- Fixa running MCP server follows edits to
.squiggle/config.jsoncandconfig.local.jsonc, solaunch_appstarts the app and simulator the files name now - Fixeach screen's interface is checked against its own testIDs, so a nested stack's
indexno longer fails Home's - Fixthe recreated-context rule names the fields that changed and no longer flags memoized providers or values that change with real navigation
- Fixread-only text and an input that isn't editable or takes no touches are no longer counted as controls
- Fixa 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
- Fixa simulator command that hangs stops with
E_SIMCTL_TIMEOUTand says how to recover, including create, boot and shutdown - Fixa new simulator's first flow is no longer covered by Expo's developer menu
- Fixevery hint to boot a simulator names
squiggle device simulator boot - Fix
squiggle initinstalls 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 acatalog:React Native - Fixa failed
initmarks each change done, failed or not applied, instead of showing every planned change as done - Fix
squiggle doctor --quickreports 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 - Fixthe agent kit's session hook shows what
doctor --quickfound, its simulator guard blocks only a command that erases or deletes a simulator, andagent kit --installsays when the MCP server isn't registered yet