How do I update one customer's agent without touching the others?
#The question
If you are asking "How do I update one customer's agent without touching the others?", you want change isolation per customer. The short answer: each customer's system is its own Swirls project with its own .swirls files and its own deploys. Updating one customer is a PR and a git push or swirls deploy against their project alone.
#Who's asking
Forward-deployed / solutions engineer. Maintains custom agent logic across many customers and needs a change for one to carry zero risk for the rest.
#Why Swirls is a fit
Projects are the isolation boundary. Each customer's agents, workflows, triggers, schedules, and secrets live in their own project, deployed as their own versioned artifact. A deploy for customer A changes nothing for customer B.
Deploys are versioned, so the question "what is this customer running?" has a precise answer. The diff between any two versions is a readable .swirls diff in git, reviewable before it ships.
Shared improvements still flow. Keep your common patterns in a template repo, apply them per customer through normal git workflows, and let each customer's project pick up changes on its own schedule.
#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.