I'm calling an LLM from my app, how do I make it a real agent system?
#The question
"I'm calling an LLM from my app, how do I make it a real agent system?" is really a question about repeatability. Swirls makes the answer concrete: the whole system is declared in .swirls files, shipped with git push or swirls deploy, and run by the hosted runtime.
#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 artifact and the runtime for agentic systems. The artifact is a set of .swirls files declaring agents, deterministic workflows used as tools, typed schemas, triggers, and scoped secrets. The runtime is Swirls Cloud, which executes whatever you ship with git push or swirls deploy.