Changelog

What’s new in Squiggle: every feature, every fix and every speed-up, newest first. The desktop app, the CLI, the MCP server and the SDK all ship on one version number, so a release here is a release everywhere — update once and you have all of it.

Screenshots and colour checks, device controls, and one project per app

0.6.818 November 2026

Fixes for 0.6.7. You can take a screenshot from the CLI or as a flow step, check a colour on screen, and run a flow on an app without the JS SDK. Flows can clear an app's data on the iOS simulator and restore a save slot, send the app to the background, post audio-session events and turn on Reduce Motion or Reduce Transparency. Each project and each checkout keeps to its own app, Metro, simulator and port: Studio, another project's agent or another worktree no longer takes, names or acts on your app. A busy screen's graph keeps up with the screen and repairs itself after lost events, and Studio no longer grows to gigabytes over a long session or stalls under a heavy event stream.

Some behaviour changed. Studio's relay serves an app only to a squiggle command or agent whose project owns it (lists its bundle id under apps in .squiggle/config.jsonc, or built its development bundle in the project folder); an older squiggle command is refused, so update it with npm install -g @squiggle.sh/cli@latest (or update Studio if you use the command that comes with it) and restart any squiggle mcp server. MCP tools refuse arguments they don't take instead of ignoring them. --strict-assert fails a run when a passing assert step holds a pending or unsupported assertion. A tap on a target that is covered whole is refused with target_covered. Healing never moves a step onto a sibling row (row-4 for row-45). The default swipe takes 200 ms instead of 300 ms. setPermissions ends a running app before a change iOS would end it for and relaunches it, and skips a change that already holds. squiggle card refuses a file that isn't in the repository (E_CARD_FILES_MISSING) and a scope with nothing to check (E_CARD_NOTHING_TO_CHECK). An app launched on its own port, or with one in its bundle, connects to that port alone and joins only its own project's Squiggle. Squiggle never uses a Metro of another checkout or one that names no project folder, and never picks a simulator another checkout's config names or another project's agent drives unless you name it. Node text is read up to 2,000 characters instead of 80, and a render count includes the first re-render after mount, so counts can be one higher than before.

Desktop app

  • FixStudio's memory no longer grows with every app reload or relaunch (several GB after a day)
  • Fixthe device relay keeps forwarding under a heavy event stream, and listens again after a Metro reload
  • FixStudio stays off a simulator another checkout or another project's agent uses unless you pick it, and its device panel says when every booted simulator is in use elsewhere
  • Fixa flow's taps are never saved as rage taps, whichever command ran it (squiggle card, bench, an MCP call)
  • Fixa refused squiggle update request logs why

Agents & MCP

  • Newdescribe, find, logs, assert and screenshot { sample } take udid to read another simulator without driving it or moving the session
  • Newlogs { source: 'native' } and squiggle logs --source native [--system] show the app's NSLog and other native log lines
  • Newreport_card takes root, so it cards a worktree's changes; without it, it runs in the checkout that owns the app
  • Newlaunch_app { fresh: true } relaunches the app (as relaunch: 'always' does) and always says whether it relaunched and on which Metro
  • Newwhen the installed CLI is updated under a running MCP server, every tool result says once to restart it, and status.server reports both versions

Performance

  • Newmemory is sampled through every step and on every screen change, so memoryDelta judges the app's footprint over a long repeat
  • Newfootprint by category (Malloc, Untagged VM, …) appears in perf report, perf budget and the report card's memoryCeilingMb row; SQUIGGLE_MEMORY_BREAKDOWN_S=0 turns it off
  • Newthe worklet UI runtime's heap is recorded as WorkletUiHeapBytes, and perf heap --ui / perf_heap { runtime: 'ui' } snapshots it; audio worklet runtimes are not measured
  • Newperf heapdiff shows the shortest path from the GC roots to each growing type, and --name (MCP name) traces a type that isn't the biggest grower
  • Fixperf heap and perf profile take the app you name or are attached to, not the store's newest session
  • Fixyour Metro's own requests are no longer counted as your app's network traffic
  • Fixa render count no longer misses the first re-render, and an app relaunched within a step counts its renders afresh

Everything else

  • Newsquiggle screenshot [name] [--udid] [--source] [-o] saves a screenshot of a simulator, a mac: app or a web: tab into .squiggle/screenshots/
  • Newthe screenshot: <name> flow and intent step works on every target (takeScreenshot is its alias)
  • Newscreenshots keep the app's own colour profile (16-bit Display P3) when the app is in front with no keyboard or alert over it, and fall back to the simulator's screen otherwise
  • NewMCP screenshot takes udid to shoot another simulator without moving the session, and says when the shot was taken (takenAt, and the step it fell in during a background run_flow)
  • Newassert: { color: { of | backgroundOf | at, is, tolerance, wideGamut, luminance } } and MCP screenshot { sample } read a colour off the screen, and wait up to 2 s for it to settle; an iOS simulator draws in sRGB, so wideGamut: true there fails and says to check on a Mac app
  • NewlaunchApp: { clearState: true } works on the iOS simulator: it empties the app's data and resets its privacy settings, keeping the keychain, app groups and your save slots
  • NewloadSlot: <name> restores a save slot from squiggle save or the MCP fixture tool inside a flow
  • Newbackground: { ms } (flow step, MCP device { background }) sends the app home and brings it back, and fails if iOS ended it meanwhile
  • NewaudioSession: { interruption: began | ended, shouldResume } or { routeChange: <reason> } posts the notification iOS sends your app
  • NewreduceMotion: true|false and reduceTransparency: true|false flow steps, squiggle device reduce-motion|reduce-transparency on|off and MCP device { reduceMotion, reduceTransparency }; a running app's AccessibilityInfo listener sees the change
  • Newsquiggle flow <flow> --native-only runs a flow on an app without the JS SDK, through accessibility and simulator input, including screenshot: and colour asserts; a step it can't run is refused before the run with E_NATIVE_ONLY
  • Newa drag leg takes assert, checked during its pause while the finger is still down
  • NewtextMatches and textNumber on a control with no text of its own read the texts inside it
  • NewlegibleContrast: { text: true } judges the contrast of every displayed text, and legibleContrast: { within: <selector> } judges the text and controls inside one element
  • Newsquiggle card --accept-renders (or report_card { acceptRenders: true }) accepts render growth you reviewed; render growth is compared launch with launch, and its baseline moves forward once a run's render rows pass
  • Newsquiggle update works when the CLI ships inside Studio: it updates Studio, launching it in the background if needed, and prints the new version
  • Newsquiggle up --metro <url|port> opens the development build on that Metro
  • Fixeach worktree uses its own Metro, simulator and port: a scan never picks another checkout's Metro, a relaunch moves the app off one, and doctor --quick fails a checkouts row when a session of one checkout drives another's simulator
  • Fixan app launched on its own port no longer also connects to Studio's :7777, including after a flow --race or doctor --fix relaunch
  • Fixstatus, target, launch_app, held-device errors and doctor name only apps your project owns; another project's app reads "an app this project doesn't own"
  • Fixyour agent never closes a dev menu or accepts an "Open in" alert that belongs to another project's app
  • Fixa worktree's own MCP session no longer holds its app against that worktree's CLI (E_DEVICE_HELD)
  • Fixa run takes its app back when the same app reconnects after its connection closed, and a disconnect names only a Squiggle the app was connected to
  • FixsetPermissions no longer passes and leaves the app to be ended by iOS a moment later, which failed the next step
  • Fixsquiggle mcp no longer writes warnings to stdout, where your agent's client read them as broken lines
  • Fixflow --matrix, --predict and --breakpoints use the run's simulator, not the first one booted
  • Fixa run waiting on a Studio that serves another simulator says so once, not on every retry
  • Fixtext past 80 characters or 8 parts is read, and a text cut at 2,000 characters is marked textTruncated; text: and textMatches match on its prefix and a miss says it was cut
  • Fixafter lost events the graph rebuilds itself and reads stale until it has; a repair no longer leaves ghost nodes or <unknown:N> names, and on iOS a consumer that falls behind is caught up instead of left minutes behind
  • Fixa window-overlay sheet or modal opened from a pager page is in the graph at its real position, and a visible miss says why (covered, on a page the pager doesn't show, or a stale graph)
  • Fixevidence.eventId starts again after a relaunch, and a fresh session cites the newest event
  • Fixa list of about 17,000 items or a very deep tree no longer loses the end of the graph, and tag / identify data nested past 32 levels or circular is cut ([nested too deep], [circular]) instead of dropped
  • Fixchecked: and selected: read accessibilityState and aria-* on React Native, including through a wrapper with the testID
  • FixnotVisible passes on a component that draws nothing, and visible fails on it saying so
  • Fixan uncontrolled input that can't be read as a text field reports what it reads instead of "cannot read that view"
  • Fixa tap on a partly covered target (a scrim behind a card) aims at the part that shows
  • Fixa tap whose screen reacts late (Appearance) or repaints off React under the finger is no longer failed as no_reaction
  • FixscrollUntilVisible and autoScroll reach rows below a bottom sheet's fold
  • Fixa swipe keeps its speed to the lift, so a bottom sheet moves to the next detent
  • FixlegibleContrast and noBlankFrame say whether controls were unmeasured or missed by accessibility instead of "on other screens", noBlankFrame reads a screen's text when it has no controls, and the checks under a sheet take a fraction of the time
  • Fixlegibility no longer flags Gesture Handler 3's LeanReanimatedNativeDetector, or the face inside a labelled icon button
  • Fixa component the last green run never rendered is a warning ("no baseline yet"), and growth at launch fails as "at launch"
  • Fixa release build with the SDK installed from npm and EXPO_PUBLIC_SQUIGGLE_ALLOW_RELEASE=1 connects (Expo 58)
  • Fixa release build that never connects is not relaunched on a Metro, and the run says what is missing (the SDK, the native library or the opt-in)
  • Fixwhen your app's JS failed to load, the run quotes the red box and Metro's error instead of blaming a port
  • Fixa flow's stopApp no longer quits the browser squiggle up holds
  • Fixsmooth counts only frames dropped while the motion runs, and web taps no longer wait out Squiggle's own frame loops

Shared ports, simulators of your own and startup holds

0.6.713 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

  • Fixintent_wait streams 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 launchApp and a relaunch to heal a stale agent
  • Fixrun_flow keeps the first screen's slow useEffect spans
  • 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

  • Newsquiggle 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
  • Newoffers a simulator of your project's own and records its udid in .squiggle/config.local.jsonc; --create-simulator does it without asking
  • NewtextMatches 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
  • 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.jsonc and config.local.jsonc, so launch_app starts the app and simulator the files name now
  • Fixeach screen's interface is checked against its own testIDs, so a nested stack's index no 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_TIMEOUT and 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
  • Fixsquiggle 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
  • Fixa failed init marks each change done, failed or not applied, instead of showing every planned change as done
  • Fixsquiggle 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
  • Fixthe 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

Startup profiles, testID props and crash lists

0.6.613 November 2026

Fixes for 0.6.5. Every launch of a development build keeps its startup profile, from the CLI and from your agent, and a run says why when there is none. agent validate follows any prop into a testID, such as testIDPrefix, and reads the items of a mapped list, so a typo fails again and correct selectors built that way pass. perf_crashes lists each crash once. A slow useEffect names its component.

Some behaviour changed. A testID the check can't read now makes a selector uncertain only when that testID could produce it, so a typo elsewhere fails instead of warning. A component call that doesn't pass a prop no longer counts as rendering a testID built from that prop. Your agent's watch keeps the startup profile without opening a debugger connection, so it keeps no stall profiles after startup; perf profile still records whenever you ask.

CLI

  • Fixsquiggle agent validate follows any prop used in a testID, such as ` ${testIDPrefix}-${option.id} `, to the values passed where the component is used, across your app and shared packages
  • Fixa testID built inside .map() over a constant list, or a list passed as a prop, takes each item's value, including through .filter(), .slice() and .sort()
  • Fixa testID the check can't read only makes selectors it could produce uncertain; other unknown selectors fail with the closest match

Performance

  • Fixevery launch of a development build keeps its startup profile when your agent runs a flow (run_flow), and when the CLI's debugger connection opens late; perf profile --startup and perf_profile { startup: true } return it
  • Fixwhen a launch keeps no startup profile, the run says why: the window expired, was already read, wasn't sampled, or couldn't be read
  • Fixa slow useEffect span names its component and the file that defines it
  • Fixperf_crashes, squiggle perf crashes and Studio's crash list show each crash once, even if it was stored twice before, and a crash report is stored once however many scans find it at the same moment

Dev menu, startup profiles and slow Metro servers

0.6.512 November 2026

Fixes for 0.6.4. A tap on Expo's developer menu no longer crashes your app on iOS 26 and waits for the menu to finish sliding in, describe lists every item in it, and a tap that changes nothing on UI outside your app says so. Every launch keeps its startup JavaScript profile, perf profile keeps recording across a reload, and perf_crashes lists every stored crash. agent validate reads only your app's own source and follows a testID built from a prop. Squiggle waits for a Metro server that is slow to answer, and never wakes, relaunches or takes an app another project's Squiggle session is driving.

Some behaviour changed. Every app Squiggle launches starts with Expo's three-finger long press for the developer menu turned off; your build saves that setting, so it stays off when you open the app yourself. Shake, Cmd-D and Ctrl-D still open the menu, and you can turn the gesture back on in the development build's launcher (Settings, Three-finger long-press). agent validate run inside a monorepo app reads only that app's src, app and components folders and your shared packages/*, never a sibling app, so a typo it used to downgrade to a warning now fails. A launch of an app another project's session drives, including flow --fresh and launch_app with a simulator you name, is refused with E_DEVICE_HELD. In navigation contracts, a screen a tour finished with no way out now fails the dead-end check instead of staying inconclusive: tour it again or list it under terminals.

Desktop app

  • FixStudio saves a crash with its incident whenever the app's process dies, not only within 12 seconds of the connection closing

CLI

  • Fixsquiggle agent validate reads your app's own folders and packages/*, never a sibling app in the monorepo; --source still sets the files to read
  • Fixa testID built from a prop inside a template, such as ` ${testID}-${image.key} `, takes the values passed where the component is used; a pattern with no letters or digits of its own is reported as unreadable instead of matching everything
  • Fixa native control with no React source, such as a photo picker's Add or a search field's clear button, passes once a run has reached it
  • Fixa selector with a flow variable, such as ${TASK_ID}-row, uses the flow's env: values and must share fixed text with your source; a selector made only of variables is skipped
  • FixSquiggle waits up to 30 seconds for a Metro server whose status answers but whose manifest is slow, and says what it is waiting for; set metroUrl in .squiggle/config.jsonc to skip the check
  • Fixsquiggle flow --fresh refuses to relaunch an app another project's session drives, with E_DEVICE_HELD, and squiggle up skips such simulators
  • Fixsquiggle perf crashes lists your app's stored crashes across sessions
  • Fixin navigation contracts, a screen a tour finished with no way out is a dead end with a counterexample
  • FixSquiggle never recreates a project folder you removed in order to save into it

Agents & MCP

  • Fixdescribe lists every item of Expo's developer menu, and tap reaches each of them
  • Fixperf_crashes lists the newest 20 stored crashes of your app on its simulator, each with its session, and marks the ones it just found; a crash report is stored once
  • Fixperf_profile keeps recording when your app reloads, instead of stopping at the reload
  • Fixan idle agent server never wakes or connects to another checkout's copy of your app, or an app another project's session drives
  • Fixlaunch_app refuses to relaunch an app another project's session drives, even on a simulator you name, and says so when it can't tell who holds the app
  • Fixthe watch reports a crash whenever the app's process dies, including after a reload and when the crash report takes longer than 12 seconds to appear

Flows & device

  • Fixa tap on Expo's developer menu no longer crashes your app on iOS 26
  • Fixa tap waits up to 1 second for a sheet that is still sliding in or out, so a tap on Close right after the menu appears closes it
  • Fixa tap on UI outside your app that leaves it unchanged for 2 seconds while your app stays silent fails with "the tap did nothing"
  • Fixwhen something covers the control you tap, the error names it accurately: Expo's developer menu as a sheet your app presents in a window of its own, and an alert or overlay by its label
  • FixopenLink after stopApp says your app has not reconnected and names no screen, instead of the screen from before the stop
  • Fixa screen with a paused animation, such as a blur held at part strength, no longer keeps a step waiting for the app to settle, so a back that changes nothing answers in about 2 seconds instead of 6

Performance

  • Newevery launch of a development build keeps its startup JavaScript profile. squiggle perf profile --startup and the agent's perf_profile { startup: true } return the newest one with its hottest functions, and Studio's flame graph lists it

Links, closing sheets and testID checks

0.6.412 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

Alerts, header buttons and monorepo roots

0.6.311 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

  • Fixan app in a monorepo is named after its repository, and its icon is found in an app.config.ts too
  • Fixthe device header's Inspecting label no longer runs over the screen name

CLI

  • Fixin 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
  • Fixin 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
  • Fixthe testID check in agent validate, affected_by_diff, crawl --changed, find and legibility --fix also read your shared packages' src, app and components folders
  • Fixwhen 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"
  • FixSquiggle 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
  • Fixan unexpected error prints its type, message, run id and stack, and a command that fails without an error exits 1 instead of 0
  • Fixsquiggle 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
  • Fixsquiggle doctor lists your project's own port first and marks ports other Squiggle sessions hold
  • Fixnavigation 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
  • Fixmotion --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

  • Fixyour 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
  • Fixtap answers ok: false with "the tap did nothing" when your app's control doesn't react, with or without expectRoute
  • Fixbatch takes device steps
  • Fixinspect and renders on a control with no React component behind it (a navigation bar button) say so, instead of "matches more than one element"
  • Fixstatus stops listing a CLI run whose process was killed

Flows & device

  • Fixwith 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
  • Fixrole: beside label: narrows the label: { label: Sign out, role: AXButton } matches the button labelled Sign out instead of every button
  • Fixa tap on a button in the navigation bar (a headerLeft view) presses it; a tap now holds still the way a finger does
  • Fixback waits for a swipe-back's transition to finish, up to 5 seconds, before it judges whether the screen changed
  • Fixa 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"
  • Fixfind and tap reach the items of Expo's developer menu, so tap: { text: Reload } works

SDK

  • Fixin 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

Taps and checks prove what they say

0.6.211 November 2026

Fixes for 0.6.1. A tap waits until your app's JavaScript is free and fails when the app doesn't react, a check sees only what is on screen, touches from two Squiggles or Studio take turns, and when your app never connects Squiggle says why. Studio's update relaunches Studio by itself.

Some flows that passed in 0.6.1 now fail, because the step now proves what it says. A tap your app doesn't react to fails with "the tap did nothing": mark a tap that is meant to change nothing optional: true. A tap's expectRoute fails when the app doesn't reach that screen within 5 seconds. A combined waitFor waits for every condition you give. role: AXButton also matches your app's own buttons, so two buttons with the same label are reported as ambiguous. text no longer matches part of a longer text your app shows, in checks and taps alike, and label has to match the whole accessibility label. A react-native-pager-view page that isn't showing is no longer visible or tappable. In a monorepo, an app with its own .squiggle folder is now its own project.

Desktop app

  • Fixthe update card shows when a release was published in your own time zone ("yesterday at 20:57"), shows progress as soon as you press Update now, and relaunches Studio on the new version by itself; a second press no longer closes the card, an error stays on screen, and Later keeps Update available in the title bar
  • Fixthe Updates row in Settings says when an update is downloading, installing or waiting to relaunch

CLI

  • Fixwhen your app never connects, Squiggle tells apart a bundle that is still building (it waits, and says so), a bundle without the Squiggle SDK (it says how to add it), a bundle that includes the SDK but never ran it, and a Metro that is up but slow, instead of pointing you at a red box or a stopped Metro
  • Fixsquiggle doctor waits up to 30 seconds for your app on a simulator, longer while Metro is still building the bundle, and says when the bundle has no Squiggle SDK, instead of waiting forever
  • Fixon a heavily loaded Mac, Squiggle waits longer for its agent to start in your app, and if it still doesn't answer, says the agent is slow and gives the load average, instead of telling you to reinstall; an app that quits right after launching is reported as such
  • Fixa run whose app crashed says so, with the exception, where it happened and the crash report's path; crash reports are matched to the simulator the run used, so another session's crash of the same app is no longer stored with your run or listed by squiggle perf crashes
  • Fixsquiggle probe eval and the other probe commands print E_JS_BUSY or E_JS_UNOBSERVABLE and exit 2 when your app's JavaScript stays busy or Squiggle can't find its process, instead of reporting a Squiggle crash
  • Fixsquiggle agent validate blocks a flow only on a recording of an earlier run of that same flow, not on an incident or another flow's recording; a screen it learned under an older short name counts as seen; and it reports a runFlow file it can't find
  • Fixin a monorepo, an app that keeps its own .squiggle folder (with a config.jsonc, flows or interfaces) is its own project, so squiggle flow, squiggle contracts and the MCP server read it without SQUIGGLE_PROJECT_ROOT; squiggle init writes into whichever folder the app already uses
  • Fixperf.db cleanup works in small steps, so other Squiggle processes writing the store no longer wait seconds or lose writes; if another process does keep it locked, a run prints one line naming the processes instead of one "database is locked" line per write
  • Fixa run that loses its app to an MCP server started before you updated Squiggle names it as an older version and tells you to update it

Agents & MCP

  • Fixlaunch_app with relaunch: "always" relaunches an app that is stuck before its JavaScript loads, such as on the Expo development launcher, and run_flow takes fresh: true to do the same before a run
  • Fixstatus and screenshot work with no app connected, and status says why nothing is
  • Fixthe tap tool takes expectRoute and answers ok: false when the app doesn't reach that screen
  • Fixrun_flow names a failed sub-flow's step as failedStep
  • Fixrun_flow can remove a row the run created, such as a queued prompt, when your app's buttons render an inner button with the same test ID and label
  • Fixthe watch skips recording an incident for disk space only when the disk holding your project has less than 2 GB free, and says how much was free; a recording that can't be saved for another reason says that reason instead of "low disk space"

Flows & device

  • Fixa tap waits, for up to three seconds, until your app's JavaScript is free and the renders it was working on have landed, so it no longer lands on a busy screen; an idle app pays nothing
  • Fixa tap on one of your app's controls that gets no reaction to either touch fails with "the tap did nothing" and shows what was under the finger each time, instead of passing with a warning
  • Fixa tap with expectRoute fails when the app doesn't reach that screen within 5 seconds after the tap lands; before, a tap didn't check it, so a tap that pressed the wrong control, or nothing, passed
  • Fixa combined waitFor passes only once every condition holds at the same moment, and a timeout says which ones did; appRunIdle waits on its own, like visible and ms
  • Fixtext matches the same way in checks, waits, conditions and taps: in your app it has to match a whole text, and a styled run inside a sentence counts as its own text. Text your app draws natively, or that another app draws (a file picker cell, a natively rendered markdown paragraph), still matches when its accessibility label contains it. So notVisible: { text: Needs attention } passes while a card reads "1 needs attention", and a tap on that text doesn't tap the card
  • Fixlabel always has to match the whole accessibility label, in any case
  • Fixa selector's role matches in either naming: AXButton matches your app's buttons as well as iOS's, and button matches a native alert's buttons; AXImage and image, AXSwitch and switch, and AXSlider and slider pair the same way
  • Fixwith the 0.6.2 SDK, a button you put in the iOS 26 bottom toolbar with Stack.Toolbar.View is tapped where it is drawn after a JavaScript reload too, instead of at the top of the screen
  • Fixwith the 0.6.2 SDK, a react-native-pager-view page that isn't showing (react-native-tab-view uses one too) is no longer on screen to Squiggle: visible fails for a control on it, describe leaves it out, and a tap on it fails as not found
  • FixscrollUntilVisible no longer drags when its element is already on screen but still moving, for example right after a tap turns a pager, so the pager stays on the page you opened
  • Fixback waits for an app that reports its new screen late before judging the result, so it no longer says the screen didn't change, or taps a back button on the screen it already returned to
  • Fixa runFlow file not found beside the flow that names it is looked up in .squiggle/flows, and a missing one fails with the paths it tried; a failed sub-flow, loop, branch or retry names the step that failed, with its kind, selector and message
  • Fixa network.stub step right after launchApp: { relaunch: always } reaches the relaunched app; a stub step that fails says whether the app runs without network capture or its Squiggle agent didn't answer
  • Fixan in-app browser opened full screen lists its Done button and Format Options, and a tap on controls iOS draws over your app (an in-app browser, a share sheet, a system alert) is about a second faster
  • FixSquiggle's taps no longer leave a finished touch behind in your app, which could crash it in iOS's gesture handling when a real tap, such as one on an alert button, followed
  • Fixtouches from two Squiggles, or from Squiggle and Studio, take turns on a simulator, including touches sent through the simulator itself (alerts, sheets, system buttons); one that waits more than 2.5 seconds fails with input-busy instead of pressing anyway

Taps, selectors and permissions do what the flow says

0.6.110 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

  • Newsquiggle 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
  • Newsquiggle flows --udid runs a suite only on the simulators you name; udid in your config or SQUIGGLE_UDID names one too
  • Newshards in .squiggle/config.jsonc, or in a profile, sets how many simulators squiggle flows uses; --shards still wins
  • Newsquiggle logs --since takes a duration, such as 2m
  • Fixthe 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
  • Fixsquiggle 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
  • Fixsquiggle 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
  • Fixsquiggle init leaves an existing Squiggle server entry alone under any name, including one Claude Code reads from a parent folder or ~/.claude.json
  • Fixsquiggle device permission opens the app again when iOS closes it to apply the change
  • Fixsquiggle motion follows a view the tap brings in, such as a sheet

Agents & MCP

  • Fixrun_flow uses the flow's own config: { autoScroll }; an autoScroll you pass still wins
  • Fixa worktree app's run_flow recording is saved in the worktree that owns it, and a refused recording names that project
  • Fixthe production rule lets a run remove what it created itself, such as a prompt it typed, and its refusal says what would lift it
  • Fixthe device tool opens the app again when iOS closes it to apply a permission change, and says so with relaunched
  • Fixa live motion track follows a view the tap brings in, instead of refusing it
  • Fixmotion 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
  • Fixa 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

  • Newa 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
  • Fixa 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
  • Fixa 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"
  • Fixa swipe on a control waits for the screen to settle, so a swipe down right after a sheet opens closes it
  • Fixan in-app browser's Done button is listed and tappable, and an iOS 26 toolbar search field is listed by its placeholder
  • Fixevery 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
  • Fixassert: { store: … } compares a value with true, false or text, and store: { useCart: {} } checks that the store exists
  • Fixyour editor flags exactly the flows, programs and config Squiggle refuses, and fetches the current schema instead of keeping its first copy
  • Fixthe agent no longer crashes an app while Squiggle stops it, which showed up as a crash report for a run that passed

Smooth motion, every screen size, and two-finger gestures

0.6.010 November 2026

Squiggle tells you whether a scroll or an animation is smooth, frame by frame, from a recording or live on the app, and a flow can fail when it isn't. squiggle flow gains checks for a screen's layout at every text size and width, for its gestures and springs, and for a busy JS thread, reordered responses and calendar dates. Flows and your agent can pinch, drag along a path and keep the on-screen keyboard up, your agent reads the app's console and changes the simulator's settings, and a web or Mac app your project declares opens by itself when a run needs it.

Some flows that loaded in 0.5.5 now stop with a parse error that names the mistake, instead of running a step that proves nothing: an assert with no check, a pressKey with no key, a key on any other step, a delivery other than auto, real or runtime, a when: with a key other than visible, notVisible, route or true, a waitFor timeout that isn't a whole number of milliseconds or auto (such as 10s), and a scrollUntilVisible maxScrolls that isn't a positive whole number. An intent program with config, secrets or tags is refused. A runFlow file named inside a sub-flow is now found beside that sub-flow's file, not beside the flow the run started from, so fix any path written the old way. To name a step, use note:: a label: is the accessibility label of the control to act on whenever nothing else in the step names one. In a monorepo, squiggle init writes .squiggle at the workspace root: move a .squiggle folder an earlier init left in your app's folder.

Desktop app

  • Newthe Devices list shows your project's web app as Not open before any window shows it, and choosing it opens Squiggle's window
  • Newthe Devices list and the device menu show your project's Mac app as Not running when it is stopped, and choosing it launches it with Squiggle
  • NewGo to screen sits in the device panel, named by the screen the app is on: it lists every screen grouped the way the app nests them, with a search, and walks the app to the one you choose. It and the inspect-element button show only while the app is live. Reload JS moves to the device menu
  • NewTunings says what each record is, what it changes and how it went, and Preview a setting shows, on a screen Squiggle captured, which controls a setting moves as you drag it
  • NewSettings has Connect your agents, which connects the coding agents it finds to the open project
  • Fixwith several simulators booted and no --udid, a run of the project uses the device Studio shows
  • FixStudio's window keeps the width its open side panels need, so the right panel no longer runs past the window's edge
  • Fixthe Renders table's hover card opens over its row and holds still while the table scrolls, and Your code lists only your components
  • FixStudio no longer freezes when it trims a large component graph
  • FixStudio's findings for an app built with React Compiler no longer advise useMemo

CLI

  • Newsquiggle init asks once to connect the coding agents it finds: Claude Code, Copilot, Codex and Cursor. --yes connects them all, --agent claude,codex names the ones to connect (none for none), and --agents-only connects them in any folder without setting up the app
  • Newsquiggle device changes the simulator from a terminal, like Studio's device menus: appearance, contrast, text-size, status-bar, location, permission, button, shake, and keyboard on, off, default or status to keep the on-screen keyboard showing while you type from the Mac
  • Newsquiggle logs prints the app's console lines your project saved, a worklet's console.log included. --level, --text, --limit and --since filter them, and --follow prints new ones until you press Ctrl+C
  • Newsquiggle motion --video <file> judges a screen recording, one of Squiggle's or any mp4: how far the content moved each frame, and each stall, dropped or repeated frame, jump, judder or reversal with its time and frame numbers. It exits 1 when the motion is janky. --region and --ignore choose what to measure, --chart draws speed over time with the bad frames marked, and --against compares with a baseline and exits 1 only when it got worse. On a Squiggle recording, each problem says what your app was busy with. When something else in the frame moves on its own, such as a spinner, it warns and names the --region or --ignore to pass. Needs ffmpeg
  • Newsquiggle flow --breakpoints finds where a screen's layout changes. On a web page it moves the width from 320 to 1280 px and lists each width where a control appears, disappears, moves to another row or changes how it grows; on an iOS simulator it runs the flow at each of the 12 text sizes; on a Mac app, or an iOS simulator with --breakpoints-range, it lays the app out at each width up to the screen's. --breakpoints-prove marks every width proven, falsified or inconclusive for controls that overlap or leave the screen, and --breakpoints-save saves and runs two flows either side of each web breakpoint
  • Newsquiggle flow --matrix --predict runs the flow once, predicts what the matrix would find at every text size, then runs the setups it flags and a sample of the rest to check the prediction, and says how many of your saved sessions each problem would reach. --predict-widths, --predict-heights, --predict-expansion (longer labels, as a translation makes them), --predict-keyboard, --predict-breakpoints, --predict-steps, --predict-prove and --predict-funnel predict more. Needs a debug build on an iOS simulator
  • New--repair works out the tunable values from the screen's layout and measures only those, instead of trying value after value; an app that can't capture its layout is searched the old way. --repair-landing-check checks each in-between state of a change that moves several tunables, and --repair-control measures what each search spends
  • New--busy-js <ms> runs the flow again with your app's JS thread held busy before every step (--from-step picks where it starts), and lists each step that breaks
  • New--reorder swaps the order in which each pair of in-flight requests answers, and lists each swap that fails the flow or changes its last screen
  • New--clock moves your app's clock (in a debug build) to each calendar landmark over the next 400 days (--clock-days sets another span), such as month and year ends, 29 February and daylight-saving changes, and finds where the screen's text changes
  • New--confirm-jank mutes the timer a periodic-jank finding names, runs the flow again, and says confirmed when the beat is gone
  • New--gesture-map <testID> finds, to the degree, where a drag on a control gives way to scrolling its list, and fails when a gesture has less than --gesture-margin degrees to spare
  • New--scroll-sweep <testID> and --drag-sweep <testID> (with --drag-by) list where each element's position bends or jumps as a list scrolls or a finger drags, and fail when an element jumps. A scroll sweep also fails when a sticky element lets go or an element is never wholly visible
  • New--motion runs the flow twice watching every view, fits each element's motion as a spring, and fails on a value that jumps or views from one line of your code that run different springs
  • New--stub-delays <match=ms,…> with --stubs answers chosen endpoints after the delay you give and prints each screen's time to ready beside the prediction, and --cpu-throttle with --cliff on a web page runs the sweep with the page's CPU slowed
  • New--record-fps sets a recording's frame rate (60 by default, 30 in a browser tab), and --record-tail keeps recording after the last step
  • Newsquiggle bench --breaks lists where a flow's time changed, and gives a slowdown between two commits with the squiggle bisect command for that range. A bench also compares each phase and step at the machine load of the run it is compared with, keeps each step's render count, and says how much render time a change in your components' renders adds or saves
  • Newsquiggle card has a layout row from the screen's last --predict-prove run, and its network row says how long a screen took at the latencies your real sessions measured. A screen budget's network entry (readyMs, latencyUpToMs) sets how fast the screen must be ready however slow your server gets, and the card checks it
  • Newsquiggle contracts navigation checks the navigation your project declares under navigation in .squiggle/config.jsonc against the screens Squiggle has recorded: each check proven, falsified with the shortest path that breaks it, or inconclusive. --reproduce saves each falsified answer as a flow and runs it
  • Newsquiggle product screens --cost ranks screens by what they cost your real sessions: dropped frames on the worst tap and time to interactive, times the share of sessions that open each screen. When a cliff's size names the state that holds it, --cliff and the card say how many real sessions reach it
  • Fixwith several simulators booted and no --udid, a run uses the device your project's MCP session drives, else the one running your app
  • Fixsquiggle init in a monorepo writes .squiggle at the workspace root, where squiggle flow and the MCP server read it. Before, the squiggle flow smoke it suggested failed with E_NO_FLOW_FILE
  • Fixan app in a yarn, pnpm or bun workspace is set up with that package manager, not npm
  • Fixsquiggle flow auth/login runs the flow in the auth folder, the name run_flow and the library use, and a .yml flow runs by its name
  • Fixsquiggle doctor checks the Metro that serves your app, not a fixed port 8082
  • Fixsquiggle up --url gives the page its full 30 seconds to connect however long the browser takes to start, and a browser window Squiggle opens quits and leaves no profile behind when Squiggle stops
  • Fixsquiggle bisect and squiggle bakeoff send the app back to the Metro it was on, whatever its port
  • Fixsquiggle probe --udid mac:<bundle id> reads a Mac app running beside a simulator app on the same Metro
  • FixSquiggle finds your app's Metro on any port, not only 8081 to 8090, for runs, status, squiggle up and the perf tools, and metroUrl in .squiggle/config.jsonc names one
  • FixSquiggle never attaches to another project's app that dials its port, and squiggle up never opens another project's Metro that shares your Expo slug
  • Fixa relaunched app comes back on the Metro it was on, a stopped dev-client app comes back on its project's Metro rather than the launcher, and the launcher opens your app's Metro even when your config names no bundle id
  • Fixan app dialling a different port is found, named and moved to the run's port, instead of a silent wait. A stopped app is reported as stopped, and a port is blamed only when the app is running and dialling elsewhere
  • Fixport 7777 held by a Squiggle process that has stopped or is leaving comes free on its own, squiggle up hands it to an agent that asks, and status names who holds it, including a Studio too busy to answer
  • Fixa relaunch keeps network capture on, and the stubs a flow set survive a relaunch inside it
  • Fixa run that changed a browser tab's viewport puts back the configured one when it ends

Agents & MCP

  • Newthe motion tool says whether a scroll or animation in a recording is smooth, frame by frame, as squiggle motion --video does. With testID, it follows that view on the running app at every frame the screen draws, around a tap or a scroll, with no recording. Each problem says what the app was busy with in those frames, against compares with a baseline, and chart adds a picture of speed over time that publish_evidence can attach
  • Newrecord_start { video: true } films the steps you drive yourself to an .mp4 until record_stop. fps and tailMs set the frame rate and keep filming after the last step, on record_start and run_flow { record } alike
  • Newthe logs tool reads the app's console, a worklet's console.log included, filtered by level and text, and since returns only newer lines
  • Newthe device tool reads and changes the simulator settings in Studio's device menus: appearance, contrast, text size, status bar, location, permissions, hardware buttons, shake and the keyboard
  • Newon an iOS simulator, the on-screen keyboard opens when your agent's field takes focus and stays up while it types, as it does for a person. device { hideKeyboard: true } puts it away, and device { softKeyboard: false } types as a hardware keyboard
  • Newthe pinch and drag tools pinch with two fingers about a control, and drag one touch along a path of up to 32 legs before lifting
  • Newan approvals block in .squiggle/config.jsonc lets your agent go on past a blocked step without you: in agent mode a sign-out goes through, and a delete goes through when your agent says why it is safe or deletes something the run created. The approvals tool sets the mode for the rest of the session, and approve_action { remember: "session" } approves a control for the rest of it. The deny list and the production rule still hold
  • Newsquiggle mcp --http <port> serves the MCP server at http://127.0.0.1:<port>/mcp, so an agent that is already running connects by URL. --http 0 takes a free port, and --host listens beyond this machine
  • Newa drive tool launches your project's iOS app when it is installed but stopped, and its result says so. A Mac app your project declares is launched with Squiggle when a run or a tool needs it, with no squiggle up first
  • Newa React web app opens in Squiggle's window when a flow, your agent or squiggle up needs it, and the window stays open until you close it. In CI, or with SQUIGGLE_HEADLESS=1, the window belongs to the run and closes when it ends
  • Newrun_flow, library_list and library_save take root, so an agent working in a git worktree runs and saves that worktree's flows
  • Newwhen your app shows a red box after a Fast Refresh edit, every tool result and status say so at once, with the line it came from, and a flow step that meets it fails instead of timing out
  • Newrenders { mounts: true } also lists what mounted and what each mount cost, and perf.db keeps mounts
  • Newpropose_fix { rank: "saving" } lists the components whose memo misses and render storms cost the most render time, with what a fix would save, and measure records what it really saved
  • Newwhat_if with condition: layout says what the screen does at another width, text size or tunable value, without touching the app, marked predicted or inconclusive
  • Newwait_for waits for a control to appear (visible) or go away (notVisible), and invariants { action: navigation } checks your declared navigation
  • Newwatch.mute in .squiggle/config.jsonc, or incidents { mute }, keeps a detector or a component off your agent's notices
  • Fixlibrary_list answers at once, and run_flow refuses an unknown flow name at once with E_NO_FLOW and the closest names, with no wait for an app
  • Fixrun_flow with waitMs runs the flow in the background: waitMs: 0 returns a run id at once, and describe, screenshot, perf_profile and perf_heap work while it runs
  • Fixperformance findings no longer crowd tool results: one line per detector, told again only when a finding gets worse
  • Fixa tap or input_text sent while its target is still moving waits for it to stop, so a tap right after typing lands
  • Fixtwo identical controls can each be targeted: nth is accepted, and a refusal over an ambiguous match offers a ref and selector for each
  • Fixinspect reports where a component is drawn on screen, or why it has no frame
  • Fixperf_insights replies with a compact summary that fits the reply limit, folding repeats of one finding, with detail by index
  • Fixperf_sql waits for rows still being written and says when this server isn't the one recording the app
  • Fixfilmstrip lays out up to 36 columns, each tile shows the frame at the time on its label, a second call renders its own sheet, and with no video named it reads only a recording made in this session
  • Fixstatus and incidents report only the incidents of the app your agent drives, not another app on the same simulator
  • Fixan MCP server started in a git worktree reads that worktree's flows and saves its app's data there, and root wins over SQUIGGLE_PROJECT_ROOT
  • Fixlaunch_app { udid } picks the simulator, and an agent whose app stops stays on that simulator and launches it there again, instead of asking which booted one to use
  • Fixperf_profile and perf_heap find your app's Metro, and say what React Native's "multiple hosts" refusal means
  • Fixa memo-miss finding no longer lists library components when Metro was down at the end of the session

Flows & device

  • Newassert: { smooth } takes jankFrames, stallMs and smoothness, read by following the element at every frame for ms, so a flow fails when its motion gets worse. An element that never moved fails the check
  • Newa pinch step zooms in or out with two fingers, and a doubleTap lands as one double tap, so a photo viewer can be driven like a phone
  • Newa drag step walks a path in one touch, so a sheet can be pulled down, back up and down again before it is let go
  • Newa hover step runs a control's hover handlers on a web or Mac app, and leave: true moves off it
  • Newa showKeyboard step opens the on-screen keyboard on an iOS simulator and keeps it up while text is typed
  • Newa step takes the name and arguments of the MCP tool that does the same: inputText types, wait pauses, waitFor takes timeoutMs, and a step name Squiggle doesn't know names the closest one it does
  • NewwaitFor: { ms } pauses, and scrollUntilVisible takes a timeout
  • Newan intent program can open a deep link with an openLink step
  • Fixa tap that puts a text field in focus counts as its reaction, so field taps are no longer sent twice and flagged "no graph reaction"
  • Fixa tap waits for what onPress did, not for the button's pressed style, and a type with submit waits for what Return does, so the next step reads the changed screen
  • Fixa tap that got no reaction because its target moved is pressed in the app on the retry, and the step says how it landed
  • Fixtyping into a field that is still loading waits for it and types again, and fails as never ready instead of reporting every key dropped
  • Fixa tap by testID or ref on a header or toolbar item, including an iOS 26 bottom toolbar item, lands where iOS draws it, and the search field iOS draws in the navigation bar can be tapped and typed into
  • Fixa link wrapped in Expo Router's zoom transition can be tapped by its testID
  • Fixa selector means the same in a flow, an intent program and the MCP tools: label is the accessibility label everywhere, and point takes "x, y" (points or percentages) or [x, y] (fractions of the screen) on every surface
  • Fixa ${VAR} is replaced in every string a step holds, so waitFor: { visible } and when guards find a testID built from a variable
  • Fixyour app's own full-window overlay or modal hides the screen beneath it: describe no longer lists what it covers, and a tap there is refused
  • Fixa swipe runs as slowly as its duration asks instead of at most 1 second, takes a point, and never starts on a screen edge iOS keeps for itself
  • FixdroppedFrames reads only frames measured after the step began, so a cold launch's jank no longer fails the first tap
  • Fixback taps the header's back button when the edge swipe doesn't navigate, in flows and over MCP
  • Fixan openLink that reloads the app waits for it to reconnect, waitFor and wait_for keep waiting through a reload within their timeout, and iOS's "Open in …?" prompt is pressed for you
  • FixwaitFor: { animationIdle: true } settles while a text field has focus: the blinking cursor no longer counts as motion
  • Fixa run's first tap waits for a screen that mounts a beat after the prerequisite
  • Fixan inline flow's runFlow and addMedia paths start at the project folder, on the CLI, MCP and Studio alike
  • Fixa network.stub step no longer passes while the app runs without network capture, and squiggle flows turns capture on when any flow stubs or waits for the network
  • Fixnetwork capture passes upload progress, authentication challenges and redirects back to your app
  • Fixyour editor accepts every flow Squiggle accepts, including a goal written as a mapping and delivery: runtime, and flags what Squiggle rejects
  • FixonStuck: abort is accepted everywhere and runs as fail
  • Fixa recording of a gesture that changed mid-touch replays what the finger did, and a recognizer that failed is no longer recorded as a tap

Performance

  • Newthe periodic-jank finding names a JS thread that blocks on a beat, and what leads it: a timer with the line that scheduled it, a polled request or a garbage collection
  • Newthe idle-periodic-work finding names work your app repeats on a beat while nobody touches it, such as a timer, named by the line that scheduled it, or a spinner that keeps running where no one can see it
  • Newa CPU profile names Squiggle's own frames [squiggle] … and reports their time apart from your app's, and Squiggle does less work in your app while a profile or heap snapshot records. Its own share of a render storm is 30% smaller

Product analytics

  • Newa near-miss friction finding marks a tap that reached nothing followed by a tap right beside it that worked

SDK

  • Newevery session records the device it ran on: the model, the OS and its version, the window size and the appearance. Text size and locale are recorded only when the user's state consent allows it, and always in a development build
  • FixSquiggle's agent no longer crashes an app that is reconnected to while it launches, and a relaunched dev-client app no longer stays black when a tool asks about it while it starts
  • Fixthe SDK no longer holds on to stores, caches, components, sockets or motion captures your app has dropped, and hook timing no longer grows your app's memory on every render
  • Fixa screen that was popped mid-search no longer measures its content 116 pt below where iOS draws it
  • Fixa release build that keeps Squiggle sees every component and names itself, and a build without it says why
  • FixSquiggle never adds a .squiggle folder or its .gitignore to a project nobody set up
  • Fixa relaunch after a simulated crash report is no longer recorded as "App crashed: XPC_EXIT_REASON_FAULT"
  • FixStudio's CLI and the npm CLI carry the same agent for a version, so they no longer each relaunch your app to replace the other's

Licensing

  • Fixsquiggle activate with SQUIGGLE_LICENSE_TOKEN set checks the runner's CI place and claims no seat. A CI job doesn't need squiggle activate

Everything else

  • Fixin a Niteshift task, the app connects when its launch file is pushed, status no longer shows a stale-agent blocker that no relaunch clears, and the Linux MCP server no longer warns about a missing agent

Waiting for the network turns on network capture

0.5.51 November 2026

A flow that waits for the network to go idle now turns network capture on by itself, the way a flow that stubs the network does. Before, such a flow run without --capture-net left the wait pending and still passed.

You can drop --capture-net from scripts that keep it only for waitFor: { networkIdle: true }. If you run with --strict-assert, a step left pending now fails the run.

CLI

  • Fixa flow with waitFor: { networkIdle: true }, directly or in a flow it runs, turns network capture on, and relaunches an app that is running without it
  • Fix--strict-assert (or config: { strictAssert: true }) fails the run when a step is left pending for lack of data, as well as when a step could not be performed

Agents & MCP

  • Fixrun_flow relaunches an app running without network capture when the flow waits for the network to go idle, and says so in its result

Flows that stub the network run on Expo dev-client apps

0.5.41 November 2026

A flow that stubs the network now runs on an app built with Expo's dev client. In 0.5.3, Squiggle relaunched the app with network capture, and the run then waited until it timed out, or with --fresh, ended in E_CONNECT with your bundle never loaded.

Nothing to change in your app: update the CLI. You don't need a new SDK or a rebuild.

CLI

  • Fixa flow that stubs the network no longer waits until --timeout after relaunching a dev-client app: Squiggle opens your bundle and the run carries on
  • Fixthe first run in a project gives up waiting for the app after 30 seconds, instead of waiting without end
  • Fixwith network capture on, a dev-client app whose Metro runs on a port other than 8081 loads its bundle. Before, every request in the app stalled for about 6 seconds, the dev client gave up and showed its launcher, and Metro logged "Packager status check timed out"

Network stubs work however your app was opened

0.5.31 November 2026

A flow that stubs the network now works even when your app was opened from its icon, from Xcode or by a previous run: Squiggle relaunches the app with network capture before the flow, from the terminal and from your agent's run_flow alike. Before, every network.stub step failed with "stub not applied", even with --capture-net.

Nothing to change: you no longer need --fresh or --capture-net for flows that stub the network.

CLI

  • Fixa flow that stubs the network, directly or through a flow it runs, turns network capture on by itself, and relaunches an app that is running without it
  • Fixa refused stub says why: stub not applied (<url>): the app was not launched by Squiggle with network capture
  • Fixa run no longer crashes with "srp: client disposed" when the dev-client launcher opens your bundle and the app reloads its JavaScript
  • Fixsquiggle up --if-needed --capture-net relaunches an app that is running without network capture, instead of reporting it ready

Agents & MCP

  • Fixrun_flow relaunches an app running without network capture when the flow stubs the network, and says so in its result
  • Fixrun_flow no longer reports "the relaunch did not fix it" after a relaunch that worked

SDK

  • Fixthe SDK reports its real version. Every earlier SDK reported 0.0.0, so squiggle doctor warned that it differed from your CLI: update the SDK in your app to clear the warning

Squiggle links on React Native 0.88 and any Nitro from 0.35

0.5.231 October 2026

Squiggle's native library now builds into your app against your own React Native and NitroModules, so a Debug build links on React Native 0.88, where 0.5.1 failed with undefined JSI symbols. The SDK works with any react-native-nitro-modules from 0.35, instead of only 0.37.

If you stayed on 0.5.0 because your app is on React Native 0.83 or older (Expo SDK 54 included), you can update: keep the Nitro version your app has, or use 0.36.5 if you have none. After updating, reinstall your pods.

SDK

  • NewSquiggle's native library links on React Native 0.88 and newer
  • Newthe SDK works with any react-native-nitro-modules from 0.35, and pod install stops with the version it found if your app's is older
  • Newsquiggle init keeps your app's Nitro when it's 0.35 or newer, and otherwise adds the newest one that builds on your React Native: 0.37.1 on React Native 0.84 or newer, 0.36.5 on 0.83 or older

Studio's compact mode goes anywhere

0.5.130 October 2026

Compact mode gains a Go to screen menu that takes your app to any screen and signs in on the way, and it offers your recent and pinned simulators when no device is running. Your app stops flashing Metro's "Refreshing..." banner while Squiggle works.

The SDK now needs react-native-nitro-modules 0.37.1: run bun add react-native-nitro-modules@0.37.1, then reinstall your pods. Nitro 0.37 doesn't build on React Native 0.83 or older with static frameworks, which includes Expo SDK 54. If that's your app, stay on Squiggle 0.5.0 for now.

Desktop app

  • Newcompact mode has a Go to screen menu: turn it on in Customize bar. It lists your app's screens by navigator and takes the app to the one you pick. If the app lands on a sign-in screen on the way, Studio runs your saved login or sign-in flow and carries on; with no such flow, it waits for you to sign in. Screens that need parameters, such as order/[id], aren't listed
  • Newcompact mode with no device lists your last three simulators and your pinned ones, each with a button that boots it, and has Exit compact mode
  • Newcompact mode's device menu opens with a Status section: screen size, frame, agent, host, CLI and session
  • Newcompact mode's bell turns toasts off and on. Alerts still reach the notification centre and still play their sound, and hovering the bell opens the notification centre

SDK

  • Newapps on NitroModules 0.37 use Squiggle's native connection instead of the slower fallback
  • FixwithSquiggle keeps Metro from watching the .squiggle folder, so your app no longer shows "Refreshing..." each time Squiggle saves a result. Restart Metro after updating

Everything else

  • Fixnavigate steps, the Screen map's Go there and Go to screen move a web app that routes in memory, such as React Navigation on react-native-web, to the screen. Before, only the address changed and the app stayed where it was

Setup is the SDK, and your agent watches the app

0.5.029 October 2026

Adding the SDK is the whole setup for an iOS app: a debug build on the simulator starts Squiggle by itself, so squiggle up is optional, the first performance baseline is taken on your first run, and updating Squiggle needs no rebuild. Your agent's MCP server now watches the app the whole time it runs and tells the agent what broke, with a recording of it. Squiggle also runs inside a Niteshift task.

A release build of your app carries no Squiggle unless you set "release": true in .squiggle/config.jsonc. In CI, the runner must be able to reach license.squiggle.sh over HTTPS on its first licensed command.

Desktop app

  • Newcompact mode has an App menu with Reload JS, Open link from clipboard and your recent links
  • Newthe device heatmap labels the drags Analytics reads as a gesture, such as "Swipe to dismiss"
  • FixRelaunch app, Relaunch injected, the permission switches and the launch after a boot act on your app, not Squiggle's example app
  • Fixreloading Studio no longer crashes it or leaves the loading banner stuck

CLI

  • Newsquiggle agent watch --incidents prints one line per recorded incident, so an idle agent can wait for the next one
  • Newsquiggle release frees the app from whatever holds it, including a run waiting for an agent's answer
  • Fixsquiggle flow --from-recording -o <file> creates the file's folder when it doesn't exist
  • Fixsquiggle crawl skips controls named "Log out" and "Check out", as it does "logout" and "checkout"
  • Fix--fresh captures the app's log output, so log asserts work after a relaunch
  • Fixevery error message names a fix you can run, and an agent port already in use is E_AGENT_PORT_BUSY
  • Fixa device command on Linux with no device provider says how to reach a device, instead of asking you to build a macOS helper

Agents & MCP

  • Newthe MCP server watches the app from the moment it starts, the way Studio does. When the app throws, crashes or stalls, it records the moment, and your agent's next tool result says what broke, at which line of your code, and which of its own actions it followed
  • Newlive performance findings, such as a render storm or a long task, reach your agent the same way while the app runs
  • Newthe incidents tool lists what was recorded, each one replayable with replay_recording, and squiggle://incidents serves the newest ones
  • Newwatch in .squiggle/config.jsonc sets whether the server watches, how it tells your agent (push: notice, channel or none), whether it records, and how much it keeps. SQUIGGLE_WATCH=0 turns it off for one run
  • Newpublish_evidence puts screenshots and recordings in the description of a pull request you opened, and needs no app running. squiggle init --pr-evidence turns it on
  • Fixthe safety rail checks the control a tap actually lands on, not only the selector your agent sent

Flows & device

  • NewsetLocation and setPermissions run on the iOS simulator
  • NewtoggleAirplaneMode is in the published flow schema, so your editor stops flagging it

SDK

  • Newa release build gets a stand-in for the SDK: the same exports with none of its code, and Squiggle's native library links into Debug builds only. Set "release": true in .squiggle/config.jsonc to keep Squiggle in a release build
  • Newa production build of a web app gets a 10 KB stand-in for @squiggle.sh/react, with no setup

Everything else

  • Newa debug build of your app on the iOS simulator loads Squiggle's agent by itself, so you no longer run squiggle up before driving it. squiggle init no longer adds it to your ios script
  • Newyour first squiggle flow, squiggle flows or run_flow records the first performance baseline when the project has none
  • Newafter you update Squiggle, the next squiggle flow brings your app's copy of the agent up to date and relaunches the app if it still runs the old one. squiggle doctor --fix does the same
  • Newsquiggle flows launches your app itself, from the appId in your flows or apps.ios in .squiggle/config.jsonc
  • Newrun Squiggle in a Niteshift task: set "device": { "provider": "niteshift" }, and the CLI and MCP server on the task's Linux sandbox drive the app on its simulator. Steps outside the app, such as a launch or a system dialog, go to the task's agent
  • Newin a Niteshift task, nothing leaves the sandbox on Squiggle's initiative: no telemetry, crash reports or update checks, and publish_evidence writes its files for the task to attach
  • Newsquiggle doctor says when the app's agent comes from another release, and squiggle bench never compares a run on a Niteshift simulator with a local one
  • Fixa CI runner that can't reach license.squiggle.sh stops with E_LICENSE_UNREACHABLE (exit 3) and names the host to allow, unless it got a place with the same token in the last 24 hours. Before, it ran unlicensed
  • Fixa CI runner is counted by a random ID kept in ~/.squiggle, never by anything about the machine, and keeps its place for as long as a long run or an MCP session lasts
  • Fixa project's .squiggle/config.jsonc can turn telemetry and crash reports off for everyone who clones it, never on. Studio asks again when you switch to such a project
  • Fixan incident recording stops 20 seconds or 8 MB after its trigger, the same problem again isn't recorded twice, and old data is cleaned up during a long session

React web apps

0.4.027 October 2026

Squiggle drives React web apps. Open any react-dom app with squiggle up --url, and the flows you wrote for your iOS app run on it unchanged, with nothing to install in the app. Studio, your agent's tools, performance and product analytics all work on a browser tab, and the CLI runs on Linux.

@squiggle.sh/react-native now carries everything your app needs. Remove @squiggle.sh/nitro from your dependencies, and load the Babel plugin as @squiggle.sh/react-native/babel.

Desktop app

  • NewStudio lists each browser tab that squiggle up --url opens beside your simulators. It mirrors the tab, and you can click, type and scroll in it, pick components and record taps
  • Newthe Devices list has a Web filter while a tab is open
  • NewPerformance has a Web Vitals lane, and LCP, INP and CLS tiles when a session recorded them. The platform filter offers Web
  • Fixa device whose app isn't connected says Waiting for app, not another device's app

CLI

  • Newsquiggle up --url <address> opens a React web app in a Chrome, Chromium or Edge window that Squiggle drives, with nothing installed in the app. squiggle up 5173 works too, and in a project whose app is a web app, a bare squiggle up finds its dev server
  • Newname a web app's address, browser, channel and window size under web in .squiggle/config.jsonc
  • New--production drives a production build you serve locally, and --maps <dir> reads its source maps when the server keeps them back
  • New--browser picks the browser by path or command name
  • Newsquiggle init sets up a Vite or Next.js app, and squiggle doctor says why a web page doesn't connect and how to fix it
  • Newsquiggle add screen writes the web version of each template, and a Next.js page for it
  • Newsquiggle crawl, squiggle motion, squiggle probe, squiggle save and squiggle load work on a browser tab. A save keeps the page, its stores, local and session storage, cookies and IndexedDB
  • Newsquiggle flows --shards N runs N flows at a time on a web app, and squiggle bisect and squiggle bakeoff with --platform web serve each commit from its own dev server
  • Newsquiggle benchmark --suite web scores your agent on a browser tab
  • Newsquiggle probe replay --udid web:<origin> replays a flow in Studio on a browser tab Studio has focused
  • Newthe CLI runs on Linux, x64 and arm64: npm install -g @squiggle.sh/cli. A Linux machine is licensed by its machine ID
  • Newsquiggle bench spaces the runs in a series 1.5 to 3 s apart at random, and records the machine's load with each run, so a busy machine is not mistaken for a slower app
  • Fixsquiggle gate relaunch listens on the port from your config
  • Fixsquiggle probe replay --udid refuses a device Studio isn't focused on, instead of failing to find Studio
  • Fixsquiggle up --url restarts Chrome when it hangs before opening a window

Agents & MCP

  • Newyour agent drives a browser tab the same way it drives an app: target, status, describe, find, tap, screenshot, inspect and the rest
  • Newdeterministic_session turns off a tab's animations and pins its locale
  • Fixprobe_read answers a program whose data is large, instead of waiting until its deadline
  • Fixreport_card runs its flows instead of failing to connect

Flows & device

  • Newemulate: { userAgent } sets the browser tab's user agent, its User-Agent header and the client hints it implies. emulate also takes viewport, colorScheme and locale
  • NewlaunchApp: { seed: { cookies, localStorage, sessionStorage } } opens a web app with cookies and storage already in place, so its first page load reads them. Cookies take the same fields as Playwright's addCookies
  • Newthe device commands run on a browser tab: location, orientation, offline, permissions, scripts, screenshots, recordings and file uploads
  • NewaddMedia puts a flow's files in the iOS simulator's photo library and On My iPhone, where the photo and document pickers find them
  • Newselectors take checked, selected and expanded, such as { testID: remember, checked: true }, on a web app
  • Newa route selector such as (tabs)/index matches a web address that never spells the group, so your iOS flows' routes work on the web
  • Newnetwork stubs, chaos and --twin work on a browser tab, including requests a service worker answers from its cache
  • Newassert smooth, the scroll blank-area check and memoryDelta measure a browser tab
  • Fixa tap on an iOS 26.4 share sheet lands on the control it names
  • Fixa hidden match no longer makes a visible one ambiguous
  • Fixsquiggle flow --headless drives the simulator --udid names
  • Fixa selector with a field Squiggle doesn't know points you to the selectors page on squiggle.sh

Performance

  • Newa browser tab records Web Vitals, its frame rate, CPU and heap, network requests with their phases, storage reads and writes, console lines and errors
  • Newthe detectors fire on a web app: slow screens, stalls, memory leaks, request waterfalls, JS-driven animation, render storms and memo misses, each naming your source line
  • Newa stall on a web app arrives with its CPU profile, named by the hook and line that ran
  • Newperf profile, perf heap, perf crashes and perf symbolicate work on a browser tab, through its source maps
  • Fixa symbolicated JS frame names the column the code is at, not the one after it
  • Fixa stretch over which the frame rate held steady reports that rate, not "frames unmeasured"

Product analytics

  • Newtaps and drags on a web page are captured, so recordings, the heatmap and friction findings work on the web
  • Newthe --platform filter accepts web

SDK

  • New@squiggle.sh/react connects your own browser, or any browser, to Squiggle. Add its plugin for Vite (@squiggle.sh/react/vite), Next.js (@squiggle.sh/react/next), webpack and Rspack (@squiggle.sh/react/webpack), or esbuild and Bun (@squiggle.sh/react/esbuild). It runs only in development: a production build carries none of it
  • Newtransport: 'proxy' connects a page through its dev server, for HTTPS and other machines
  • Newwith a plugin, Zustand stores are named after the variable they are assigned to, and Legend State stores are observed
  • Newon a web app, describe, find and inspect show the line that renders each element and name each hook, with no Babel plugin
  • NewRedux and Jotai stores are observed, in React Native and web apps. TanStack Query is observed in web apps
  • Newroutes come from React Router, TanStack Router and Next.js's App and Pages Routers
  • Newin a React Native development build, call sites, definitions and hook names still show when the Babel plugin's source lines are off
  • Newload the Babel plugin as @squiggle.sh/react-native/babel. It installs with the SDK, so you no longer add @squiggle.sh/babel-plugin yourself. The old name still works
  • New@squiggle.sh/nitro is no longer needed: the SDK carries its native code. Remove it from your dependencies
  • Fixa React Native app without Expo links Squiggle's native code. Before, the SDK ran without it, slower, and said nothing
  • FixSquiggle's app port refuses requests from web pages, so a page you visit can't pose as your app

0.3.024 October 2026

squiggle card tells you whether a change is done: it runs the flows that reach the screens you changed and lists each problem with the line to fix. Flows can test your app on a slow or broken network, catch a double tap that sends a change twice, and drive the photo picker, share sheet and permission prompts iOS shows over your app. Save and load put the app back on any screen, with its data, in under a second.

Two changes may need action. Squiggle saves data only for apps your project owns, so list yours under apps in .squiggle/config.jsonc. With several simulators booted, name the one to drive with --udid.

Desktop app

  • Newsave the app's current screen and data from the device panel's Capture menu, and load it back in under a second
  • Newa Tunings screen shows what squiggle flow --tune and --repair measured and what they propose
  • NewPerformance has a Probes section: write a rule, install it on the connected app, and see when it held
  • NewProduct has a State section, showing what your app held on each screen
  • NewAnalytics names the control each touch landed on, and what each drag was meant to do
  • Newthe tour has 25 chapters, folds its sections and shows how much you've read. Every chapter has a hint
  • Newmenu items show their keyboard shortcut, such as Show all devices (⌘G)
  • NewSettings are grouped into sections, and the simulator stays in view while you change them
  • Newa healed step shows how close the match was, and warns when it was close to failing
  • FixStudio checks for updates on every launch, and Check for Updates opens the update card
  • FixStudio's Replay goes to the flow's start screen first, as squiggle flow does
  • Fixzooming into a live timeline no longer jumps when the session grows, and a timeline parked at the end follows it
  • Fixhover cards on graphs stay above everything and inside the window, and close with the session they describe
  • Fixthe inspector's selection box stays inside the device screen and follows a scroll
  • Fixthe Renders table keeps the Component column in view while it scrolls sideways
  • Fixa popover over the device preview scrolls instead of the device
  • FixStudio no longer reloads an app that another tool is driving
  • FixStudio removes a recent project whose folder is gone
  • PerfStudio stays idle while an app is connected and nothing on it changes

CLI

  • BreakingSquiggle saves an app's runs, recordings and performance data only into the project that owns it: the app is listed under apps in .squiggle/config.jsonc, or its development build was built inside the project. Any other app still works live, but nothing about it is saved. If an app's data stops appearing, add it to apps
  • Breakingwith more than one simulator booted, a command that drives a device refuses to pick one and lists them (E_DEVICE_AMBIGUOUS). Name one with --udid, SQUIGGLE_UDID or udid in your config. Your agent's tools refuse the same way
  • Newsquiggle card checks whether a change is done: it runs the flows that reach the screens you changed, checks what they measured, and lists each problem with the line to fix
  • Newsquiggle add screen writes a new screen from one of six templates, with a flow that drives it and a renders budget it meets
  • Newsquiggle save and squiggle load keep the screen the app is on, with the data behind it, and put it back in under a second instead of tapping through screens
  • Newsquiggle bisect finds the commit that slowed a flow, without rebuilding the app. --hunks says how much of the slowdown each change in that commit accounts for
  • Newsquiggle bakeoff runs one flow against several revisions and compares pass rate, duration, renders, dropped frames, memory growth and startup in one table
  • Newsquiggle motion records how a view moves after a tap and gives you the withSpring config that reproduces it
  • Newsquiggle contracts propose turns what your passing runs always showed into asserts in your flows, and proposes removing an assert that stopped holding
  • Newsquiggle perf budget checks each screen's budget against the newest session, with the margin to each limit. --changed checks only the screens your branch changed
  • Newsquiggle perf labels exports every run with its outcome, heals and app state, as JSONL
  • Newsquiggle probe when runs a rule inside your app and reports when it held. squiggle probe export keeps the rule as a detector
  • Newsquiggle store audit lists data in your project that came from an app the project doesn't own. --purge removes it
  • Newthe first squiggle up in a project saves a baseline named first
  • Fixsquiggle up gets a development build past the Expo launcher, and reports ready only once the app's JS has connected
  • Fixevery command uses the port from your config or SQUIGGLE_PORT, not always 7777
  • Fixa YAML syntax error in a flow is reported as one, not as "a bug in Squiggle"
  • Fixa Ctrl-C during --matrix or --repair puts the simulator's appearance and text size back
  • Fixa squiggle bench series with a failed run records the failed run and exits 1

Agents & MCP

  • Newreport_card gives your agent the report card
  • Newbisect_state finds the store values that make a flow fail, from two save slots
  • Newwhat_if tells your agent what a flow did under a repeated tap, a Back press or a bad network, from runs already recorded, without touching the app
  • Newtune lists and sets the values your app declared tunable
  • Newproduct_state shows what your app held on each screen
  • Newbranch can start from a save slot, and tries the likeliest alternative first
  • Newpropose_fix turns a --tune or --repair result into a code change
  • Fixan idle squiggle mcp no longer uses a quarter of a CPU core
  • Fixlaunch_app gets past the development launcher and an "Open in …?" alert, and returns once the first screen is up

Flows & device

  • Newflows drive the photo picker, the document picker, the share sheet and permission prompts that iOS shows over your app. Select their controls by the text they show
  • Newsquiggle flow --twin runs a flow on a working network and again on a slow, flaky, cut-off or offline one, and reports what your app did differently, such as a spinner that never goes away or an empty state shown for a server error
  • New--fuzz breaks each endpoint the flow called, one at a time
  • New--race finds a repeated tap or a Back press, made while a request is in flight, that sends a change twice or navigates after the user left. It writes the shortest flow that reproduces each
  • New--chaos runs a flow on a bad network, and --stubs answers the network from an earlier run. A flow can declare chaos in its config
  • New--cache-twins <cold>,<warm> shows which requests a warm app answered from its cache and which it fetched again
  • New--bisect-state <green>,<failing> finds the few store values that make a flow fail, and names the lines that write them and the components that read them
  • New--matrix runs a flow in each simulator setup, such as dark mode and the largest text size, and lists the layout problems each one adds. --repair searches the values you declared tunable for a layout with no problem in any setup
  • New--tune <name> picks a tunable value, such as a list's windowSize, by measuring dropped frames at each one
  • New--cliff VAR=lo..hi finds the list size where dropped frames start to climb, and what rendered most there
  • New--boundaries checks the edges of every control and reports an edge whose touches land on something else
  • New--ax-only finds every control through the accessibility tree alone, the way VoiceOver reaches it
  • Newthree asserts: scroll (frame rate, dropped frames, blank cells), smooth (how a region moves through a transition) and memoryDelta (memory growth since the previous step). Thresholds you leave out come from the screen's budget
  • NewwaitFor waits for a control to appear or go away, so opening a sheet needs no retry
  • Newswipe takes a duration to drag slowly, and a hold to long-press before dragging, so a flow can reorder a list
  • NewsoftKeyboard: true keeps the on-screen keyboard up while a flow types
  • Newa near miss says which part of the selector scored what, and how far under the threshold it fell
  • Fixa selector with a testID and text needs both to match
  • Fixa type step waits for the text to land in the field, and checks it
  • Fixa control whose testID, label or press handler changes in place is found under its new name
  • Fixa scroll longer than its list is several drags inside the list
  • Fixa held drag starts on the control it holds
  • Perfthe wait before each step is 41% shorter, and a relaunch finishes as soon as the app shows its screen

Performance

  • Newset a performance budget per screen in your config
  • Newstartup is split into phases, each timed by the module that owns it
  • Newa JS stall comes with its CPU profile, including the first stall after a fresh launch
  • Newa wait that runs long names the component still animating, with its file and line
  • Newthe js-driven-motion finding catches an animation that moves only while JS runs
  • Fixcapturing a stall profile can no longer crash your app
  • Fixone app launch is one session, whether Studio, the CLI or both watch it
  • Fixsamples follow a relaunched app into its new session
  • Fixtwo tools recording performance at the same time no longer lose a session
  • Fixa long task that repeats is one finding per cause, grouped across sessions

Product analytics

  • Newsplit any report by a state sessions reached, with --where
  • Newsee which app states friction happens in, the states real sessions reach that no flow tests, and how states drift across releases
  • Newan abandoned drag is a friction finding

SDK

  • Newdeclare values Squiggle may tune, such as a list's windowSize, with defineTunable and useTunable
  • Newsave slots capture your Zustand, Legend State and MMKV stores without setup
  • Newstate analytics samples what your app held on each screen, as shapes rather than values. Turn it on with EXPO_PUBLIC_SQUIGGLE_STATE_ANALYTICS=1 at build time; it also needs the user's consent, which you set with setStateAnalyticsConsent
  • Fixgestures whose callbacks are worklets run on the UI thread again with the published SDK
  • Fixupgrading Squiggle no longer needs --clear on Metro
  • FixZustand stores appear under their own names, such as useCart
  • Fixa slow drag keeps its interaction until the finger lifts

Website

  • Newevery docs and changelog page has a Markdown copy at its URL plus .md, and each docs page has Copy as Markdown and View as Markdown, for your coding agent
  • Newthe templates page runs each template on the demo device and shows its report card
  • Newon a phone, the menu and the search can be dragged away

0.2.116 October 2026

Test an iOS app and its Mac app from one project, and see what re-renders and why in Studio's Renders tab. Studio checks performance while you use the app and tells you about each new problem once. The docs on squiggle.sh are rewritten, with live demos.

If your Mac app's build runs install-macos-agent.sh, remove that step: Squiggle adds the agent for you.

Desktop app

  • Newa tour of Studio, offered when you finish onboarding
  • Newthe Renders tab shows what re-renders, what caused it, and which providers trigger extra renders, and warns you about render loops. The Inspector's Perf tab is now Renders too, and the component tree highlights each re-render
  • NewStudio checks performance while you use the app, and tells you about each new problem once
  • NewInsights can group recent sessions, so a problem that keeps coming back is one card
  • Newthe Performance screen opens on a dashboard
  • NewCompare puts several metrics on one chart, with presets. Hover a metric to see what it measures
  • NewReplay charts show CPU per thread, dropped frames, garbage-collection pauses and network
  • NewReplay draws a recording's touches over the device, and the heatmap follows the playhead
  • Newcapture a CPU profile from the Flamegraph panel with one button
  • Newthe device menu lists running Mac apps
  • Newnotifications survive a restart, and clicking one takes you to what it's about
  • NewHardware → Shake shakes the simulator
  • FixStudio uses less CPU, and animations and tooltips run at the right speed
  • Fixthe Inspector no longer shows "0 nodes" for a connected device after an agent session
  • Fixhovering a row in the component tree outlines that component on the device
  • Fixexpanding a row in the Network panel no longer shows an error
  • Fixa restarted run's charts no longer start with a sample from the previous run
  • Fixtaps made by a flow or an agent no longer count as rage taps or dead zones

CLI

  • Breakinginstall-macos-agent.sh is gone. Squiggle adds the agent to your Mac app's Debug build for you, so remove any build step that runs the script
  • Newsquiggle init finishes setting up an Expo app, adding the Babel config and entry file if they're missing. Anything it can't change safely, it lists for you to do
  • Newsquiggle init no longer creates a .env file. Your iOS app finds Squiggle without one
  • Newsquiggle init --agent claude also installs the Squiggle agent kit into .claude/
  • Newsquiggle doctor also checks your licence and the Babel plugin, and says how to fix either
  • Newwhen your trial or licence expires, Squiggle tells you where to buy a key
  • Fixsquiggle perf diff --assert exits with code 1 when a threshold is breached
  • Fixsquiggle crawl exits with code 1, not 2, when it finds a crash
  • Fixtwo runs started at the same moment no longer merge into one history entry

Agents & MCP

  • Newrenders gives your agent what Studio's Renders tab shows
  • Newpropose_fix turns a performance finding into a plan of code changes
  • Fixbatch checks every step before it runs any, so a malformed step no longer runs the steps before it
  • Fixafter a filtered describe, the next action no longer reports elements that were already on screen as new
  • Fixa tap by ref hits that element, even when another one has the same label
  • Fixthe agent kit's Claude Code hooks run

Flows & device

  • Breakinga misspelt key at the top of a flow file, such as healng:, is an error that lists the valid keys. It used to be ignored
  • Newtest an iOS app and a Mac app from one project: list both under apps in the config, and pick one with --platform. squiggle init fills them in
  • Newresults are kept per platform, so a flow that passes on iOS isn't counted as passing on macOS
  • Newsquiggle flow --record works for Mac apps
  • NewMac apps with App Sandbox turned on work too
  • Fixa run for your iOS app no longer connects to your Mac app, or the other way round
  • Fixscrolling works in Mac apps, sideways too
  • Fixa Mac app left open no longer slows down the start of a run
  • FixexpectRoute on a tap no longer shows an error in your editor

Performance

  • Newfindings link to the line that declares the component
  • Newwhen a context value is recreated on every render, the finding names the context and the component that provides it
  • Newmemo-miss also catches props that are new objects or arrays with the same contents
  • Newnav-loop flags navigation loops your users don't usually take
  • Newsquiggle perf insights lists a session's findings, and squiggle perf watch shows them as they happen
  • Newperf diff --assert can fail when a finding you name appears, with failOnDetectors
  • Newperf diff and product analytics compare sessions from one platform at a time. Choose which with --platform

SDK

  • Newrage taps and dead zones are detected on every control, not only gesture-handler ones
  • Newcomponents wrapped in memo() or forwardRef() show up under their own names
  • Fixa button with no label or testID appears once in describe, not once for each component wrapping it
  • FixMac apps no longer report an impossible JS FPS

Website

  • Newthe docs are rewritten, and cover every MCP tool, agent command and Performance panel
  • Newmore docs pages have live demos you can try
  • Newsearch (⌘K) finds entries in reference tables
  • NewGet Squiggle walks you from install to your first flow
  • Fixtooltips no longer stay open after you tap on a phone
  • Fixthe phone menu lists every section of Why, Pricing and Download
  • Perfsquiggle.sh pages load faster and jump around less while they load

0.2.011 October 2026

A flow step can be a goal an agent drives: your agent works it out once, and every run after that replays it without a model. Studio's Runtime Inspector shows each component's live props, hooks and state, maps your app's screens, and Replay opens on what went wrong. Squiggle also drives react-native-macos apps, and a login flow runs in about a quarter of the time it took in 0.1.0.

Two changes may need action. MCP tool names lose their squiggle_ prefix, so update any permission grant that names a tool. A step key that nothing reads is now an error with its line number, so fix any typo it reports.

Desktop app

  • Newagentic flows: a step can be a goal an agent drives. Flows has Scripted and Agentic tabs, shows how many agent steps each flow has recorded, and edits an agent step's prompt, verifier and recording. Intent runs moved here too, replacing the Agents screen
  • Newthe Runtime Inspector: a component tree beside four views of the selection — Details, Graph, Perf and Screen map
  • NewInspector Details: a component's props, hooks and state, its context and stores, renders, accessibility, style and structure, read live from the app
  • Newedit a prop or a hook's state from the Inspector and the app on the simulator changes with it, until it reloads
  • Newpick a component by pointing at it on the device mirror; where several are stacked under the pointer, the scroll wheel walks through them and a click lists them all
  • NewFollow in app: selecting a component in the tree or the graph brings it on screen, navigating to its screen and scrolling it into view
  • Newopen the line that writes an element, or where its component is defined, in your editor
  • Newthe Inspector's Graph draws the live component graph as a tree or a force layout, with pan, zoom and the lineage of whatever you hover
  • Newthe Screen map: your app's screens and the taps between them, drawn as a roadmap with each navigator's screens grouped under its name, the screen the app is on ringed, and every screen's picture
  • NewCrawl the app from the Screen map: it presses each control in turn, maps every screen a press opens and photographs it, signing in with the values your flows type. Crawl from here starts on one screen, and the map fills in as it goes
  • NewGo to screen: pick a screen from the map or the menu, and Go there drives the app along the known path to it
  • Newfrom any screen on the map, start a scripted flow that taps its way there, or an agentic flow that starts there
  • Newthe Screen map shows which screens no flow reaches, filters to the screens reachable from where the app is, and adds the screens you open yourself
  • NewReplay, redesigned around what went wrong: Studio keeps the five seconds before a crash, error, stall or spike as an incident, and the player opens on it with a screenshot and a report you can copy
  • Newfrom an incident, explain the component it blames, open the run in Performance or Analytics, or make a regression flow from it
  • NewReplay's event list says what was tapped, swiped or scrolled, where, and what it led to, and its timeline has metric lanes for frames, activity, memory and latency, each with a legend
  • NewDrive device: scrubbing a recording, pressing an event or playing it drives the app on the simulator to the same moment
  • Newrecordings are named the way you would describe them, and you switch between them without leaving the player
  • Newa gallery for screenshots and screen recordings, with a swipeable, zoomable viewer. Screen recordings are H.264 or HEVC video
  • Newsimulator tools and real device skins
  • Newcompact mode: a small simulator-only window with its own toolbar, which you customise and reorder, and a row of live graphs
  • Newinstalling the app installs the squiggle command too: it links itself into your terminal, and offers to add it to your PATH when your shell cannot find it. Settings → Command line removes it
  • FixStudio no longer runs out of memory while the device mirror streams
  • Fixclicks on a menu or tooltip land on it rather than the control underneath, overlays open beside their control, and buttons keep working after compact mode
  • Fixthe simulator mirror takes input with no app connected, and an overlay over it no longer passes clicks through to the simulator
  • Fixre-running a flow from History uses the settings the run was recorded with
  • Fixthe notification bell reports failed runs (flows, benches, crawls, recordings, agent runs) and stays quiet about a command you typed in a terminal, which already showed its error
  • PerfStudio's idle CPU dropped from 22% to 6% of a core, and the device mirror costs about 20 points of a core less
  • Perfflows run from Studio at the same speed as from the terminal
  • Perfa 2,000-node graph pans and zooms at 60 fps, and switching tree and force layouts takes a tenth of the time
  • Perfmemory stays flat in a long session: an hour at 60 renders a second holds 11.6 MB instead of 90.7 MB, and a two-hour recording writes 130 MB instead of 968 MB
  • PerfStudio uses 43% less CPU while other tools read the app through it

CLI

  • Newdrive react-native-macos apps as well as iOS: --platform macos on every device command, and install-macos-agent.sh, shipped beside the binary, puts the agent in your app
  • Newsquiggle flow --record saves the run as a video, and an agent can attach it to a pull request
  • Newsquiggle probe reads live values from the running app's JavaScript over Metro
  • Newsquiggle crawl writes screen memory as it goes, and crawl --changed revisits only the screens a change touches
  • Newa failed step says why and what to do next, and --log <level> streams the run's events as it goes
  • Newsquiggle init --agent claude|copilot|codex registers the MCP server with the agent you use, for Claude Code, Copilot or Codex
  • Newsquiggle bench --pr <N> posts the result as a sticky comment on the pull request
  • Fixscroll no longer crashes the simulator, and it actually scrolls
  • Fixa tap on an element off screen is refused instead of landing on whatever is there
  • Fixback-to-back flow runs pass: no screens left open by the previous run, and each run starts from where its flow expects to
  • Fixa run that launched your app gives up on one that never connects, and says why
  • Fixsquiggle flows takes flow files as well as directories, and squiggle agent run <name> finds a program by name
  • Fixa react-native-macos app is driven in the background, and an action that did nothing is reported as a failure rather than a success
  • Perfsquiggle --version answers in about 20 ms

Agents & MCP

  • Breakingtool names drop the squiggle_ prefix your client already adds, so mcp__squiggle__squiggle_tap is now mcp__squiggle__tap. Update any permission grant that names a tool. squiggle_exec is now probe_read
  • Newrun_flow runs agentic flows: your agent drives each agent step once, and every run after that replays it without a model
  • Newfilmstrip reads a recording's frames, for defects the graph cannot see
  • Newdescribe and find see native views, such as an Expo Router native tab bar, that tap could already reach
  • Newan action returns the screen it just changed, so the next step needs no second look
  • Newevery tool has a display title in your client
  • Newevery element knows the line that writes it: describe {fields: 'source'} shows it, and find {callSite} shows what a line renders
  • Newinspect reads a component's live props, hooks and state
  • Fixno tool call waits forever, and one that hangs no longer blocks the rest
  • Fixinput_text waits for the field to take focus, so the tap after it lands
  • FixStudio and the CLI take port 7777 back from an idle MCP server
  • Fixa flow's secrets never reach the model, the run report or the recording
  • Fixthe agent kit's hooks and slash commands run your installed squiggle, and its plugin.json starts the server with squiggle mcp. The kit no longer carries a Stop hook that only applied to Squiggle's own repository. Regenerate the kit after upgrading
  • Perfa tap with its observation returns in 110–185 ms, and choosing the target takes 7 ms instead of 300
  • Perfperf_sql and saved queries answer within a 24 KB budget with a truncation note, instead of reading the whole table first

Flows & device

  • Breakinga step key that nothing reads is a parse error with its line number. It used to be ignored, and surfaced later as a selector that would not match
  • Newagent: steps: a goal an agent drives, checked by a verifier you write, recorded beside the flow as .agent.json and replayed from then on
  • Newdeclared routes, with route hints for agent steps
  • Newa flow can declare that it fails by design, or that it runs some other way
  • Newa flow's config: block carries the run settings it needs (scroll mode, settle and step timing, autoScroll, strictAssert), so a suite runs every flow the way it was written to run
  • Newa recorded tap names the control it pressed
  • Fixan app launched without the agent is relaunched with it before a run, instead of running slower without it
  • Fix"keep software keyboard: off" keeps it off, and a run never takes over another app on its device
  • Perfa login flow runs in about a quarter of the time: the median went from 10.9 s at 0.1.0 to 2.7 s, and 2.3 s with --direct-scroll
  • Perfsquiggle flow starts about 1.4 s sooner, and reconnects after a relaunch in 1.0 s instead of 6.2 s
  • Perfa suite spends less time resetting between flows, and its shards pull from one queue ordered by each flow's last duration

Performance

  • Newwhat Studio derives live (dead zones, scrolls, gesture tracks, the touch heatmap) is stored in perf.db, so your agent can query it
  • Perfthe metric store keeps older samples at coarser resolution, so a store that had grown to 1.5 GB now takes about 30 MB. Product reads take under 2 ms, and writes are 4× cheaper

SDK

  • NewLegend State stores are instrumented by the Babel plugin, alongside Zustand, MMKV, AsyncStorage and SQLite
  • Perfthe SDK does less work on your app's JavaScript thread, and sends about 31% fewer bytes per frame. Encoding a frame takes 122 ns instead of 360, and an app nobody connects to no longer holds 2.3 MB of memory for it

Website

  • Newtry Studio in your browser at squiggle.sh/studio, against a live demo app, with a guided tour of 21 chapters across every screen
  • Newdocs pages open on live slices of it, and every page's header opens Studio over the page you are on
  • Newon a phone, Studio plays its own tour, sized to read, with a chapter menu

Everything else

  • Perfa crawl of the example app's 18 screens takes 46 s instead of 94 s, and never leaves the app
  • Perfchecking the assertions of 421 recordings takes 3.9 s instead of 209 s, and seeking a recording is about 3.4× faster

Public beta

0.1.016 August 2026

Welcome to Squiggle. This is the first public release, and the whole idea fits in a sentence: your app already knows what it is doing — its component tree, its state, its navigation, its network, its frame times — and until now nothing was asking. Squiggle puts a small SDK inside the running app, streams all of that into one queryable model, and then QA, performance, product analytics and agents stop being four tools that disagree and become four views over the same thing.

That model is the design, not a feature of it. A flow selector resolves against it, so a renamed button re-resolves instead of going red. A slow frame and the render that caused it are two queries over the same data. An agent reads it instead of screenshots — which is why a login journey runs end to end at zero model turns, and why every claim it makes carries the session and event it came from, for you to check rather than believe.

What you install. Six pieces, one version number, one licence. Start with the SDK: everything else is a view over the graph, and nothing produces a graph until the app is instrumented.

@squiggle.sh/react-native
the SDK, and the only Squiggle code that goes inside your app. bun add @squiggle.sh/react-native, then one side-effecting import at the top of index.js. No provider, no config file, no account: the native accelerator and its single peer come along with it, idle cost is approximately zero while nothing is attached, and it checks no licence — the thing that has to be trusted enough to ship in your bundle asks nothing of you.
@squiggle.sh/babel-plugin
a devDependency, and strictly optional. It is the difference between a component name and a clickable source location, and — with MMKV v4 — between storage spans and none.
@squiggle.sh/cli
npm install -g @squiggle.sh/cli. Sixty-three commands from one typed tree, with an exit-code contract CI can branch on: squiggle init wires the SDK into an existing app, squiggle up relaunches it with the agent attached and proves it, squiggle flow runs a journey, and --json is on everything that returns data.
The desktop app
the DMG on the download page, for Apple Silicon. The Studio, the Runtime Inspector, the Performance Center and the Agent Center, plus the same squiggle binary bundled inside the app, so installing one installs both. One licence and one project store across the two.
The MCP server
already in the CLI, so there is nothing else to install. squiggle init --mcp merges the entry into your .mcp.json — your other servers survive untouched — and your agent gets seventy-five tools over one warm session, where a second question costs almost nothing.
The agent kit
squiggle agent kit --install writes skills, a subagent per mode, hooks and slash commands into your agent, so it learns how to drive your app once instead of being told each time.
A licence
squiggle activate --trial gives you fourteen days with no card. After that a licence verifies offline, on the machine, and CI takes a token instead.

What beta means here. Everything below this line works and is being used daily; beta is about the shape, not the parts. The SDK's public API is what we will be slowest to change, because it lives in your bundle. The CLI's flags, the MCP tool names and the flow vocabulary are where a breaking change is most likely before 1.0 — and every one of them will land here, on this page, with the version that made it.

Desktop app

  • Newone-click simulator bring-up, and a live canvas you can drive your app from
  • Newthe Runtime Inspector — eleven node kinds, the causality edges between them, and a render-flame tree you can scrub
  • Newsix overlay modes on the canvas, and a grid that watches several devices at once
  • Newthe Performance Center: flamegraphs, heap diffs, network waterfalls and baselines, side by side
  • Newinteraction analytics — a heatmap that knows which component was under the finger, not just where the pixel was

CLI

  • Newsixty-three commands from one typed tree, with an exit-code contract CI can branch on
  • Newsquiggle init wires the SDK into an existing Expo or bare app in one step, and is safe to run twice
  • Newsquiggle up relaunches your app with the agent attached — and proves it, rather than hoping
  • New--json on every command that returns data, so a run is pipeable into whatever you already have

Agents & MCP

  • Newan MCP server with seventy-five tools over one warm session, so a second question costs almost nothing
  • Newa runtime that executes a compiled plan and wakes the model only at the decisions that need one — a login journey runs end to end at zero model turns
  • Newevery claim an agent makes carries the session and event it came from, so you can check it instead of believing it
  • Newsquiggle agent kit --install drops the skills into your agent, so it knows how to drive the app without being told each time

Flows & device

  • Newflows in YAML, with selectors that name what a control _means_ rather than where it sits — a moved button re-resolves instead of going red
  • Newrecord a session and replay it offline, as many times as you like, against the same assertions
  • Newthree delivery planes, chosen per step, so a run is as fast as it can safely be

Product analytics

  • Newfunnels with time-to-convert, cohort retention, feature affinity and release annotations — over the same events everything else reads

SDK

  • Newone install and one import. A Babel plugin and an Expo config plugin do the rest, and nothing ships to your users

Licensing

  • Newa fourteen-day trial with no card, and a licence that verifies offline once activated