Skip to content
GitHub

HotLoop Cascade 1.2.0 release notes

1.2.0 finishes the MCP server’s tool list. The engine, the workflow file format, the screens and the REST API are what they were in 1.1.1.

Every MCP in the HotLoop family reads and writes, and Cascade’s had four routes left out that a key is allowed to call. They are tools now, 83 in all:

  • list_keys and revoke_key: the keys of the person the key belongs to, and revoking one. A key can revoke itself, which is what a leaked key’s holder should be able to do first. The route’s own checks decide whose keys a caller may revoke, the same as in the editor.
  • listen_workflow: opens a workflow’s test webhook URL for one call, for 1 to 600 seconds.
  • start_oauth: hands back the address a person opens to sign in for an OAuth2 credential. The person still has to say yes.

Each one goes through its route, so the permission check, the validation and the audit row are the route’s, and a write wants a reason like every other write tool.

Ten routes turn a key away themselves, because they want a person signed in: making an API key or a service account key, making a SCIM token, adding, changing or deleting a secret provider or a log destination, and your own password. A key that could make keys, or change where the audit log goes, is a leaked key that keeps itself alive. the MCP page has the list and the reason.

This release builds amd64 only. Multi-arch ships in its own run, so the release after this one is a single small version bump that builds both.

No migrations. helm upgrade to 1.2.0, or let :stable roll the Quadlet units. Putting 1.1.1 back is safe, because nothing in the database changed. What a rollback can’t undo is what an agent already did with the new tools.