Sign Up
Deploying agency icon

Agency Domain

Deploying Agency

Control how your agent handles shipping releases, deployments, and infrastructure changes.

The Deploying agency governs how your agent ships code to production, manages releases, and makes infrastructure changes. Deployments carry inherent risk because they affect live systems, so this is a domain where higher oversight is often warranted.

What Deploying Covers

Deploying actions include pushing code to production, creating releases, modifying infrastructure configurations, scaling services, updating environment variables, running database migrations in production, and managing CI/CD pipelines. When your agent triggers a deployment or modifies a server configuration, that is a deploying action.

Oversight Levels

Silent

Your agent deploys and makes infrastructure changes without asking. It ships when it determines the code is ready, rolls back if something goes wrong, and manages the release process end to end. This is suitable for teams with mature CI/CD pipelines, comprehensive test suites, and automated rollback mechanisms.

For example, your agent might automatically deploy a hotfix after verifying all tests pass and the change is small and well-scoped.

Report

Your agent deploys and notifies you about what was shipped. You get messages like "I've deployed version 2.3.1 to production. The release includes the new search feature and two bug fixes. All health checks passed." You stay informed and can intervene if something looks wrong.

Report works for teams that trust their deployment pipeline but want visibility into what is going live. It keeps your agent moving while giving you a clear audit trail.

Approval

Your agent prepares a deployment and waits for your go-ahead. You see messages like "Version 2.3.1 is ready to deploy. It includes these changes. The staging environment passed all tests. Should I ship it?" Nothing reaches production until you confirm.

This is the recommended default for most users. Deployments affect real users and can be difficult to fully reverse. Approval ensures you have a final checkpoint before changes go live.

When to Use Each Level

Deployments are partially reversible. You can often roll back, but depending on the nature of the change, a bad deployment might cause downtime, data issues, or user-facing problems in the meantime. The cost of a deployment mistake is usually higher than the cost of a brief approval delay.

For this reason, most users start with Approval for deploying. As you build confidence in your agent's judgment and your deployment pipeline's safeguards, you might move to Report. Silent deployment is best reserved for projects with strong automated guardrails, comprehensive staging environments, and fast rollback capabilities.