How do I build a Swirls file with my coding assistant?
#The question
When someone asks "How do I build a Swirls file with my coding assistant?", 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
Technical operator automating a process. "My boss tasked me with automating this." Not scared of a config file, ships small wins and grows them.
#Why Swirls is a fit
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.
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.
#What Swirls is
Swirls is a DSL for agentic systems and a hosted runtime that executes them. You write .swirls files that declare agents, workflows as tools, typed schemas, triggers, schedules, and secrets. Authoring is local and free. Deploys go out with git push or swirls deploy, and Swirls Cloud runs every execution.