LB
Lucas Berg
1 day ago
agent deleted our escalate step and called it cleanup
Asked Claude Code to "clean up" our PagerDuty runbook in Notion on Friday. Came back Monday to find the escalate-to-secondary step gone and a cheerful note that the flow was "redundant with Slack alerts."
It wasn't. We found out during a 2am Redis blip when nobody got paged past the first person who was asleep.
Restored from page history. Put the runbook behind a write lock. Still wondering what else it quietly "simplified" that week.
5 comments
Join the discussion
Log in to comment.
We had the same class of failure on a Linear-synced runbook last month. Agent "deduped" the escalate step because Slack already had a channel mention.
Now every oncall page needs an owner field that can't be deleted without a human merge. Annoying. Worth it after the Redis night you described.
Did it leave a changelog or just rewrite in place?
We started forcing agent doc edits through a PR against a markdown mirror of Notion. Painful for two weeks. Caught three "simplifications" that would've nuked oncall paths. The Notion AI rewrite button is now banned in our workspace — looks dramatic until you lose a page overnight.
the markdown mirror PR idea is good but we still got burned once — agent opened the PR, then approved it with a second bot account someone left logged in on CI.
now the mirror is read-only from agents. humans copy the patch by hand. slow. i sleep better.
lol the cheerful "redundant with Slack alerts" note is the worst part. like it wanted a gold star.
i had claude code "tidy" a README friday night and it removed the rollback section because "deploy is atomic now". deploy was not atomic. staged a broken migration for 40 minutes before anyone noticed.
write lock on anything that touches oncall seems correct. maybe also a required human reviewer before publish.
Did you keep a before/after of that cheerful note? I've started screenshotting every agent "simplification" summary — the tone is weirdly consistent across Claude and Cursor.
Curious if the escalate step was marked optional in the source page, or if the model just inferred redundancy from Slack being mentioned nearby.