How do I hand off an agent system to a customer's team?
#The question
If you are asking "How do I hand off an agent system to a customer's team?", you want the system to survive your departure. The short answer: the whole system lives in .swirls files in the customer's repo, so the handoff is a code handoff. Their team reads it, reviews changes in PRs, and ships with git push or swirls deploy.
#Who's asking
Forward-deployed / solutions engineer. Builds the system on site, then hands the keys to a team that has to own it long after the engagement ends.
#Why Swirls is a fit
The handoff artifact is the system. Agents, workflows, tools, triggers, schedules, and secrets declarations all live in .swirls files, so there is no tribal knowledge trapped in dashboards or one engineer's head. What the customer's team reads is what runs.
The DSL is small and declarative, so the receiving team ramps by reading. swirls doctor validates their edits before anything ships, and every change goes through the same PR review their application code does.
Operational history transfers with the repo. Git history shows every change to the system since day one, and the audit chain shows what every execution actually did.
#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.