How do I define an AI agent in a config file instead of code?
#The question
"How do I define an AI agent in a config file instead of code?" 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
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 the deployment target for agentic systems. The whole system lives in .swirls files: agents, deterministic workflows your agents call as tools, typed schemas, triggers, schedules, and scoped secrets. You author and validate those files on your machine, then ship them with git push or swirls deploy. The hosted runtime takes it from there.