My agent logic is scattered across my app code, how do I consolidate it?
#The question
If you are asking "My agent logic is scattered across my app code, how do I consolidate it?", you want this running without wiring up bespoke infrastructure. The short answer: describe the system in .swirls files, ship it with git push or swirls deploy, and Swirls Cloud runs it.
#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 the deployment target for agentic systems. The whole system lives in .swirls files: agents, deterministic workflows your agents call as tools, typed schemas, triggers, schedules, and scoped secrets. You author and validate those files on your machine, then ship them with git push or swirls deploy. The hosted runtime takes it from there.