ChangelogLinks, closing sheets and testID checks

0.6.4

Released 12 November 2026.

Fixes for 0.6.3. back no longer says the screen didn't change while your app is still catching up, a tap right after closing a sheet waits for it to go, openLink can check the screen a link opens, and agent validate understands testIDs your code computes. Your agent and CLI runs no longer take an app another project's Squiggle session is driving.

Some behaviour changed. squiggle agent validate now fails on a selector whose testID nothing in your source can render, and the agent kit's flow-edit hook sends that back to your agent; while your source has a testID the check can't read (testID={id}), such selectors stay warnings. To catch a link your app drops, add expectRoute to its openLink: without it, the step still ends on your app's first render. A session that wasn't told a simulator skips one whose app another project's session drives, and stops with E_DEVICE_HELD when no other simulator is booted; pick one with target, SQUIGGLE_UDID or --udid.

CLI

  • Fixsquiggle agent validate reads testIDs your code computes: a conditional counts as each of its values, a template such as ` option-${index} matches option-0, option-1` and so on, and a testID passed down as a prop counts where you write it
  • Fixagent validate --hook checks the edited flow's testIDs too
  • Fixa command you don't point at a simulator skips one whose app another project's session is driving
  • Fixsquiggle doctor's store in git warns only about files that .squiggle/.gitignore ignores, so baselines you commit on purpose are fine. To commit exported baselines, add !baselines/ and !baselines/** to .squiggle/.gitignore and keep baselines/first.json ignored

Agents & MCP

  • Fixyour agent never takes or redirects an app another project's Squiggle session is driving: status lists it under others with heldBy, and target refuses to switch to it. Studio and sessions of the same project still share the app
  • Fixwith several free copies of your app (for example from two checkouts), your agent picks the one your project's own Metro serves
  • Fixtap and the other actions wait for a closing sheet the same way flows do

Flows & device

  • NewopenLink takes expectRoute, like tap: the step fails unless your app reaches that screen within 5 seconds, and names the screen it stayed on
  • Fixback no longer says the screen did not change when your app reports the new screen a moment after the transition ends, for example while a screen streams content in; it still waits at most 5 seconds
  • Fixa tap right after closing a sheet, such as Expo's developer menu, waits up to 2 seconds for it to finish closing instead of failing with "selector did not resolve"
  • Fixa native control under a sheet, such as a tab or a navigation bar button, is reported as covered, naming what covers it, like any other control