Release notes, engineering deep-dives, and how we think about agentic workflows. Straight from the team writing the code.
Swirls now has agents. An agent is a block in a `.swirls` file, and its tools are workflows — so every tool call runs as a checkpointed execution under the runtime, not as a function call around it.
Swirls now exchanges JWTs from your identity provider for short-lived access tokens. No more long-lived API keys and no more guessing which user did what.
One .swirls file from the Swirls team's own GTM stack, read top to bottom. An OIDC-federated identity, a schedule, a graph with a scoped-delegated HTTP call, a durable Postgres-backed stream, and a trigger. One file. Five primitives. No long-lived API tokens. This is what a deployable agent looks like.
A declarative language and durable runtime for agentic workflows. Define forms, webhooks, AI steps, and human review in a single .swirls file. Then deploy in one command.
Write .swirls files locally. Deploy for free to inspect the project in Swirls Cloud.