Sign Up
Maintenance agency icon

Agency Domain

Maintenance Agency

Control how your agent handles updates, fixes, cleanup, and ongoing monitoring.

The Maintenance agency governs how your agent handles routine upkeep, including applying updates, fixing minor issues, cleaning up unused resources, and monitoring system health. Maintenance work is essential but often unglamorous, and letting your agent handle it autonomously can free you to focus on higher-value work.

What Maintenance Covers

Maintenance actions include applying dependency updates, fixing minor bugs, cleaning up unused code or resources, running health checks, responding to monitoring alerts, optimizing performance, archiving old data, and performing routine system administration. When your agent updates a package version or cleans up unused environment variables, that is a maintenance action.

Oversight Levels

Silent

Your agent performs maintenance work without asking. It applies updates, fixes minor issues, and keeps systems clean on its own. This works well for routine, low-risk maintenance activities where your agent has a track record of handling things correctly.

For example, your agent might automatically update a minor dependency version after verifying that all tests still pass, or clean up temporary files that accumulated during a build process.

Report

Your agent performs maintenance and summarizes what was done. You get messages like "I've updated three dependencies to their latest patch versions, cleared the build cache, and archived completed tasks older than 90 days. Everything is running smoothly." You stay informed about what changed without needing to initiate or supervise the work.

Report is a strong default for maintenance. The work needs to happen, the risk is usually low, and staying informed is valuable without being a bottleneck.

Approval

Your agent identifies maintenance needs and asks before acting. You see messages like "There are four outdated dependencies with security patches available. Should I update them?" Your agent waits for your go-ahead.

This makes sense for maintenance activities that could affect stability, like major version upgrades or configuration changes to production systems.

When to Use Each Level

Most maintenance actions are reversible and low-risk. Dependency updates can be reverted, cleaned-up resources can be restored from backups, and configuration changes can be rolled back. The cumulative value of consistent, autonomous maintenance is significant because deferred maintenance creates technical debt that becomes increasingly expensive to address.

Many users start with Report for maintenance and move to Silent once they are confident in their agent's judgment. The main exception is maintenance that touches production infrastructure or involves breaking changes, like major version dependency upgrades. For those, Approval is worth the small overhead.