Spillway 0.1.1: comments where the work is, and AI that asks first

Spillway 0.1.1 is out. It is a patch release by number, but most of it is new work from the two weeks since 0.1.0. Three themes run through it: review that happens where the content is, search that answers questions, and AI that can reach the whole site while a person stays in charge of what changes.

Comments in context

Comments are now threads, with replies and @ mentions that reach people by email and in the bell. Open the preview, press Comments on the preview bar (or the C key), click a block and write: the comment is pinned to that block, and everyone who opens the preview sees the pin. The same works from the page builder's block toolbar. Pins follow the block across revisions, and a pin whose block was removed says so instead of floating somewhere wrong. The thread's author, the item's author or an editor can resolve it.

Guest review links and a setting that holds publishing until every thread is resolved come next; the plan is in Comments in context.

Search that answers

Turn on Answers under Site settings → Search, and a search that reads as a question gets a short answer above the results, written only from your published pages, with every fact linked to its source. The new Ask block puts a question box with suggested questions on a help, admissions or contact page. When the pages do not hold an answer, Spillway says so and shows the results, rather than guessing.

Patterns in your brand

Patterns, at the top right of Components, shows every pattern editors can insert, each drawn as a live frame in your published or draft brand, light, dark or high contrast. Duplicate one to start your own, and see at a glance which ones use a block the site hides.

AI that reaches the whole site, and asks first

Until now the AI could do a great deal with content and very little else. In 0.1.1 an MCP client, with the permissions of the person whose token it holds, can work with taxonomy, redirects, alerts, shared blocks, collections, forms, sections, content types, comments and suggestions, the safe site settings, kits, the brand and modules.

Two safeguards come with that reach. Anything that deletes, publishes the brand, installs a kit or changes a module takes two calls: the first answers what would happen, in words, and a token; only the same call with that token does it, within five minutes, once. And the Site agent in the admin never makes such changes itself: it proposes them as a card in the chat, and Accept runs the change with your permissions, not the agent's. Secrets such as API keys and anything that injects code stay with people in the admin.

The full list is in the MCP guide.

Upgrading

Take a backup, pull the new image (or update the packages to 0.1.1), and restart: the migrations run on start. Upgrading in the install guide has the steps, including how to go back.