Automations
Define an agent in YAML with a cron schedule or an event trigger and it runs unattended in its own sandbox, with your repos cloned and dependencies installed. Every run is logged with cost per step, and permissions and budgets are enforced by the platform.
The prompt, the trigger, the repositories it clones, and its spend caps live in one file. Creating or changing it is a pull request, live on merge, so the review process you already have becomes the change-control process for your automation.
ellipsis: version: v1 name: Nightly migration checker description: Run api-repo's migration checks nightlytrigger: type: cron schedule: "0 3 * * *"session: harness: type: claude_code instructions: | Run `make check-migrations` in api-repo. If it fails, identify the migration at fault and open an issue with the failing output and the likely fix. environment: repositories: - name: api-repo variables: - name: DOPPLER_TOKEN budget: session: 1.50Prompt, trigger, repos, and caps in one committed file
Every tool call, every turn, and the exact instructions the agent launched with are recorded, with cost and duration per step. An automation nobody watched is still fully auditable, and the whole history is searchable.
Every turn and tool call, with cost per step
Cap what one session can spend and what the agent can spend across a day, a week, or a month. A session that reaches its cap stops and records budget_hit, and a run blocked by a trailing limit never gets a sandbox at all.
session: budget: session: 1.50 day: 5.00 week: 20.00 month: 60.00Hard caps per session, agent, and developer