How do I deploy custom agent logic from CI for each org?

Run evidence stays attachedrun and trace identified
Inspect the run, its trace, reviews, and defining source.

#The question

The direct answer to "How do I deploy custom agent logic from CI for each org?": 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

Forward-deployed / solutions engineer. Tasked with standing up custom agent logic per customer or per org, comfortable in a terminal and IDE.

#Why Swirls is a fit

Swirls files live in source control next to your application code. You review agent changes in a PR and read your operational process over time through git history.

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.

Add the people, data, authority, and decisions around this job.

Keep this solution beside the Apps, records, rules, connections, and reviews it depends on in one .swirls project.