ChangelogStartup profiles, testID props and crash lists

0.6.6

Released 13 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