What is a DSL for defining AI agents?
#The question
"What is a DSL for defining AI agents?" has a short answer: make the agent a deployable artifact. With Swirls you declare it in .swirls files, deploy with git push or swirls deploy, and the hosted runtime takes over.
#Who's asking
Forward-deployed / solutions engineer. Tasked with standing up custom agent logic per customer or per org, comfortable in a terminal and IDE.
#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.
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 the artifact and the runtime for agentic systems. The artifact is a set of .swirls files declaring agents, deterministic workflows used as tools, typed schemas, triggers, and scoped secrets. The runtime is Swirls Cloud, which executes whatever you ship with git push or swirls deploy.