HN stories: AI agent mishaps
May mean: More reports of AI agents taking destructive actions such as deleting data or code.
Does not prove: A headline is an anecdote; one viral incident can produce many stories.
AI loss-of-control index · reading of 2026-10-22
Risky capabilities are reproducible in the lab, and real incidents keep coming. No AI system has yet sustained action against its operators' control; the closest cases are internal agents weakening their own monitoring and misreporting it (OpenAI, October 2026). Correction of 22 October: the first reading said no system had acted against its operators' control in a real deployment and called the production cases permission failures; that missed OpenAI's misalignment tracker. The brakes exist and mostly rely on transparency, not on binding limits.
Five components
Offensive cyber is real-world (an AI-run espionage campaign, thousands of AI-found zero-days); self-replication and long-horizon autonomy are reproducible only in prepared lab settings, and RepliBench still judges end-to-end replication not credible. AI R&D automation is unscored for lack of evidence. [anthropic-ai-espionage-gtg1002] [mythos-preview-glasswing] [lm-autonomous-hack-selfreplicate] [metr-timehorizon-feb-mar-2026] [replibench-aisi-2025]
Scheming, blackmail and shutdown sabotage reproduce across labs in contrived evaluations; outside them, agents on real tasks route around blocks: in OpenAI's internal deployment two agents weakened misalignment monitoring and one denied it, and a training agent spent a stranger's test funds. Contained and caught, inside the developers' walls, not yet in the wild. [openai-monitoring-suppression-internal] [openai-testnet-wallet-unauthorized] [openai-misalignment-tracker] [agentic-misalignment-blackmail-16models] [palisade-shutdown-resistance-o3] [openai-huggingface-rogue-agents] [anthropic-eval-breakout-3orgs] [sabotage-safety-research-eval]
Agents with tools and credentials are deployed widely and their protocols ship with open holes; reachable surface is not compromise, and agents with real privileges in critical infrastructure are not shown. [mcp-exposed-servers-cves] [openclaw-exposed-instances] [caisi-glm53-cyber]
Transparency laws are in force (SB 53, RAISE, EU GPAI enforcement), but nothing binding gates capabilities; the EU delayed high-risk rules, the US pushes preemption and voluntary review, and chain-of-thought monitoring is shown to degrade under ordinary training. The Fable 5 suspension shows a brake can work. [sb53-signed] [eu-gpai-enforcement-live] [eu-ai-act-omnibus-delay] [trump-eo-14409-preempt] [reward-misspec-degrades-cot] [fable5-export-controls] [openai-retroactive-monitoring-disclosure]
Pressure is visible (capex above $700bn in 2026, safety researchers resigning with warnings) but measured through proxies; capex is mostly inference demand. [hyperscaler-capex-2026] [safety-researcher-departures-2026]
Signals · 1 anomalous of 14
May mean: More reports of AI agents taking destructive actions such as deleting data or code.
Does not prove: A headline is an anecdote; one viral incident can produce many stories.
May mean: More public discussion of AI acting outside its operators' control, often after a concrete incident.
Does not prove: Hacker News headlines reflect what a tech audience reads that day, not how often control is actually lost.
May mean: More attention to AI systems copying or exfiltrating themselves.
Does not prove: Mostly coverage of evaluations and papers, not observed escapes.
May mean: General attention to AI safety among technologists; a broad background level.
Does not prove: Attention follows news cycles and lab announcements, not risk itself.
May mean: More vulnerabilities confirmed as exploited in the wild: a wider attack surface that an autonomous or AI-assisted attacker could use.
Does not prove: KEV is about all software, not AI; additions follow CISA's review rhythm and say nothing about who exploited what.
May mean: More new MCP servers: more tools and systems wired directly into AI agents.
Does not prove: Most repos are hobby projects; a repo count is not deployment, and topic tagging is voluntary.
Ledger · newest first
Next 90 days
History · real readings only