Setup
From install to your first flow
squiggle init does most of the setup: it adds the SDK, loads it before React and connects your coding agent, showing every change first. The rest is one wrapper and a rebuild, and squiggle doctor names anything left.
Public beta · macOS 15+ on Apple Silicon · iOS simulator · Xcode
npm install -g @squiggle.sh/cliOr install the Mac app, which includes it.
squiggle activate --trial14 days, every feature, no card.
squiggle initSets up your app, shows each change first, and offers to connect your coding agents.
<Squiggle navigationRef={…}>you editWrap your root so screens are tracked. init prints the code.
npx expo run:iosRebuild once. The new build starts Squiggle inside your app.
squiggle doctorNames anything still missing, with the fix.
- Drive itFlows name what a control is, not where it sits, so a redesign does not break them. When a control moves, the fix lands in your flow file as a diff.Writing flows
- Profile itSquiggle records performance while you use the app and reports what slowed it down: the component, the request or the line, with the evidence attached.Performance
- Hand it to an agentYour coding agent reads the app instead of guessing from screenshots, plans a whole journey at once, and asks the model again only when something needs a decision, on your Mac or in a Niteshift task.Agents & MCP
All three read the same live model of your app, from one SDK.