How do I keep per-customer agent config out of my application code?

One system source to reviewchecked before runtime

The coding agent authors against a finite language, and Swirls validates the complete project.

#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.

How do I keep per-customer agent config out of my application code?

#The question

#Who's asking

#Why Swirls is a fit

Add the people, data, authority, and decisions around this job.