Updates

Build log

What has shipped to slurry.io and when, newest first. Everything listed is live in production.

3 November 2026

@slurry/cli 0.2.0 on npm, with sims mcp, records defects, rules export and rules apply. See Command line.
Rules as code: slurry rules export writes a simulation's rules as YAML, and slurry rules apply makes any simulation match that file.
Planted data defects with an answer key: near duplicates, casing and spacing faults, emptied fields and junk rows, so you can check that your code finds them.
State verification: when a check fails, the closest near miss is the record that met the rarest conditions.
Listing records no longer returns the revision history and file versions Slurry keeps on each record.
Webhooks refuse private IP-literal targets when each delivery is sent as well as when the webhook is registered. Slurry's response headers can now be read from a browser. See Webhooks.

A simulation is also an MCP server: its API operations become tools for the agent under test. See MCP server.
@slurry/cli 0.1.0 published to npm, with its own Command line docs page: install, sign in, CI, coding agents, grading, commands and exit codes.
Import your own records into a simulation from JSON or CSV, through the REST API, the MCP server or slurry records import.
A failed webhook delivery now says why in plain words: DNS, refused, reset, TLS, timeout, blocked or redirect.
slurry agent setup never writes through a symbolic link, and --dir must already exist.
Jira: an active sprint never starts in the future, and a live sprint rollover starts the next sprint on the board's cadence, no later than the hour it is due.

slurry eval grades an agent run in one call across several simulations, combining request, validity and state checks.
Repeatable faults: a seed makes chaos, error rates and latency jitter replay the same way every run. See Rules.
Connection-level faults: dropped connections, empty replies and malformed replies.
slurry agent setup adds Slurry to Claude Code and Cursor in one command.
Webhook deliveries can be found, read and replayed from agents and the command line.
State verification: check a simulation's records against an answer key.

slurry, the command line for coding agents and CI: simulations, request checks and test suites from a terminal.
Request validation: check the requests your system sent against the vendor's API specification.

Request checks: find and verify the requests a system made to a simulation.
Teams: no single person posts more than 450 channel messages and replies, so a channel reads like a real team.

The Simulator: describe a company and watch its working week happen.
A director decides once each working day what happens to every project in a world. Jira, Teams and the portfolio tools all follow that one story.
Each project moves at one pace across Jira and the portfolio tools, set by its health.
Meetings happen live: the director calls them and Teams holds them, with a written transcript.
Jira comments, slip reasons, blockers and new issue titles are written from what is happening in the world. Older Jira comments are rewritten from the issue as it stood at the time, and only name the people on that issue.
Background jobs report that they are alive, and rewriting a simulation's text can never fail the simulation itself.

Teams messages are written from what is happening in the world, not drawn from fixed phrase lists. Simulations made before this date can opt in.
Fluid joins the library as a simulated portfolio management API. Clarity Project and Portfolio Management (PPM) gains cost plans and benefit plans.

Earlier releases are not listed here yet.