Changelog

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.