Ace’s agents investigate incidents, prepare fixes for review, verify recovery and keep what they learn, working from one map of your infrastructure. Start with incidents.
A migration waits on a lock held by reporting
Infrastructure agent
Order delivery waits behind the same session
Telemetry agent
The migration runner retries without a timeout
Code agentdb/migrations/runner.tsPR #843await db.transaction(async (tx) => {+ await tx.sql`SET LOCAL lock_timeout = '2s'`; await applyMigration(tx, migration);− retry: untilSuccess()+ retry: boundedBackoff({ attempts: 3 })Resources, dependencies and the path an incident takes through your infrastructure.
Ace builds a graph of your connected resources and their dependencies. Its agents use the same map to find affected callers, shared databases and services that could fail next.
Infrastructure, telemetry and code agents pursue different leads at the same time and write to one shared incident record. A database finding redirects the trace search. A trace points to the change that needs review. When new evidence arrives, the investigation picks it up instead of starting again.
Ace prepares fix and revert pull requests with the incident context attached. A fix carries the patch and, when the failure reproduces, a regression test, and is reviewed for correctness, data safety and operations before it opens. If Ace's own pull request fails your checks, it makes one follow-up fix. Rollbacks, Kubernetes changes and connector actions such as a Vercel rollback go through the same plan and approval. Your policies govern execution and your engineers merge.
Ace revisits the original symptoms and checks affected dependencies. If recovery fails or the incident returns, it can open a follow-up investigation with the previous action and evidence attached. Retry budgets keep that loop bounded.
Findings, engineer feedback and action outcomes become system memory. Ace searches past incidents across your organization by meaning, not just by name, to recognize familiar failures and avoid repeating unsuccessful work. It prepares lasting fixes and regression checks for the cause behind the incident.
Begin with read-only investigations and reviewed proposals. Production changes need an approver your administrator names. Delegate supported actions by target, with approval rules and execution limits. Ace keeps the diagnosis, authorized change and observed result together, so your team can decide what to delegate next.
Each agent posts in the incident's Slack thread as its own teammate. Approve a plan with a message, ask about it, and follow each step as it runs. Coding agents can pull the full incident context through Ace's MCP server, and scheduled scans flag wasted spend in connected sources.
Watch Ace investigate an incident, prepare the fix
and verify that service recovered.