How do I track how my agent's behavior changed over time?
#The question
"How do I track how my agent's behavior changed over time?" is really a question about repeatability. Swirls makes the answer concrete: the whole system is declared in .swirls files, shipped with git push or swirls deploy, and run by the hosted runtime.
#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.
Every user and machine execution is uniquely identified, and every node type supports a human-in-the-loop checkpoint. Workflows are declarative, repeatable, and auditable by construction.
#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.