杀死开关问题：如何停止一个失控的人工智能代理

An email triage agent was deployed in a company's customer support operation to read incoming tickets, categorize them, route them to appropriate queues, and send acknowledgment emails. After successful testing and staging, the agent was put into production. However, two weeks later, a configuration error in the routing logic caused a loop: a misclassified ticket triggered a rerouting rule, leading the agent to read the ticket again and send acknowledgment emails on each iteration. By the time a support manager noticed that the same customer received 89 identical emails in 31 minutes, the agent was in its ninetieth cycle. The manager contacted the on-call engineer for a solution, but there was no documented answer. The engineer ultimately revoked the API key to stop the agent.