多数 AI 事故响应工具仍把关键决策留给人类
Most AI incident tools still leave a key decision to humans
多数 AI SRE 工具仍停留在智能体自主性的前两个阶段：被调用（copilot、聊天界面、CLI）和后台触发（定时任务、告警规则），尚未达到能自行判断何时需要关注事故的主动阶段。The New Stack 将于 10 月 22 日举办网络研讨会，Traversal 联合创始人兼 CTO Raaz Dwivedi 将讲解这三个阶段及团队信任主动型智能体所需的条件。
正文
当前显示原文，中文全文译文尚未就绪。
An AI SRE agent can help troubleshoot an incident. But can you trust it to decide on its own when something needs attention?
Most teams treat agent autonomy as a yes or no question. For incident response, it is a progression with three phases, and many agents in production sit earlier on it than the teams running them realize. Most AI SRE tools still stop short of the final phase.
On Thursday, October 22, The New Stack hosts a live webinar with Raaz Dwivedi, co-founder and CTO of Traversal and an assistant professor at Cornell Tech. His team applies causal AI and agentic reasoning to production incidents. He will walk through where the industry sits on that progression and what it takes to move up.
You have successfully registered for the webinar.
The three phases of agent autonomy
Invoked: copilots, chat interfaces, and CLIs that wait for an on-call engineer to open them and ask a question mid-incident. Background: scheduled jobs, alert rules, and triggers that fire on conditions someone predicted in advance. Proactive: agents that decide for themselves when an incident needs attention, without waiting to be invoked or scheduled.
The first two phases share a limit. Each depends on a person noticing that something is wrong, or on someone predicting the right condition ahead of time. Proactive agents remove that dependency.
What it takes to trust an AI SRE agent
Moving to the third phase raises a trust question. An agent that waits to be asked can be wrong without much consequence, because an engineer reviews the answer. An agent that decides when to engage also has to judge when to stay quiet. Dwivedi will cover what separates an agent that responds from one that acts on its own, why many AI SRE tools stall in the first two phases, and what has to be true before a team lets an agent make that call.
What changes once agents act on their own
Dwivedi will also discuss where the shift is already happening, drawing on Traversal Workers, agents that already operate at the proactive end of the progression. He will explore what changes for engineering teams once the agent in their stack stops waiting to be asked.
The session closes with live Q&A, so you can ask him your questions directly.
Join us on Thursday, October 22, 2026 at 1 p.m. Eastern / 10 a.m. Pacific, to learn where your team stands in the progression and what it would take to move up. Register today.
The post Most AI incident tools still leave a key decision to humans appeared first on The New Stack.