How do I keep per-customer agent config out of my application code?
#The question
"How do I keep per-customer agent config out of my application code?" 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
App developer using an AI SDK. Already calling an LLM from app code. Prompts, tools, and sessions are scattered across the codebase.
#Why Swirls is a fit
Your app becomes a thin consumer: a session id, a trigger, a response. Prompt assembly, tool calls, schedules, and audit move out of application code and into a deployed Swirls project.
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. 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.