How do I review agent behavior changes in a pull request?
#The question
When someone asks "How do I review agent behavior changes in a pull request?", they want a repeatable path from definition to running system. Swirls gives you one: .swirls files describe the system, and git push or swirls deploy ships it to Swirls Cloud.
#Who's asking
Platform / infra engineer. Owns how things run in production. Cares about durability, isolation, audit, and repeatable deploys.
#Why Swirls is a fit
Swirls files live in source control next to your application code. You review agent changes in a PR and read your operational process over time through git history.
Because the whole system is described in the Swirls DSL, you apply the same static analysis to agentic workflows that you already apply to code. The runtime enforces the policy you declared.
#What Swirls is
Swirls is agentic systems as code. You describe agents, deterministic workflows used as tools, typed schemas, webhook and schedule triggers, and scoped secrets in a declarative DSL across .swirls files. Deploy with git push or swirls deploy and Swirls Cloud runs the system. DSL in, running system out.