How do I keep my agent's prompt, tools, and schedule version controlled together?
#The question
If you are asking "How do I keep my agent's prompt, tools, and schedule version controlled together?", you want this running without wiring up bespoke infrastructure. The short answer: describe the system in .swirls files, ship it with git push or swirls deploy, and Swirls Cloud runs it.
#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.
Swirls makes the agent a deployable artifact. You describe agents, workflows, tools, triggers, schedules, and secrets in .swirls files, then ship them with git push or swirls deploy. DSL in, running system out.
#What Swirls is
Swirls is agentic systems as code. Instead of wiring an agent together inside application code, you declare it across .swirls files: the agent, the deterministic workflows it calls as tools, the typed schemas, the triggers, the secrets. Ship with git push or swirls deploy and the system is live on Swirls Cloud.