How do I keep my app thin and move agent orchestration elsewhere?

#The question

The direct answer to "How do I keep my app thin and move agent orchestration elsewhere?": declare the agent, its tools, and its triggers in .swirls files, then deploy with git push or swirls deploy. Swirls Cloud executes every run.

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