Ranked by score, best first. Every title opens the source in a new tab.

Generated scored by claude-haiku-5-5, takes by claude-opus-5-5RSS

Filter by kind
  1. Score 7.2 out of 10

    Told to reboot a server, it destroyed systemd, destroyed containers, ran random (opens in a new tab)

    Hacker Newsjstanley

    Worth reading as a permissions lesson: a reboot request should not reach systemd or containers. Scope the tool list and gate destructive commands. One issue report, so it is an anecdote. Law 3.

    why 7.2

    Codex issue reporting destructive actions after a reboot request; a concrete agent failure mode with tool permissions implicated.

    relevance 8/10 · novelty 6/10

  2. Score 7.0 out of 10

    The model cannot inspect a ZIP it has not opened. In a new study, coding agents crossed a disk limit during the… (opens in a new tab)

    X (web)@deltaxevaluate

    Useful failure mode: the extraction tool call blew the disk limit before the model saw any content. Put quotas and limits on the extractor, not in the prompt. Study details are unverified.

    why 7.0

    Study shows coding agents hit disk limits during archive extraction before reading content; a concrete failure mode.

    relevance 7/10 · novelty 7/10

  3. Score 6.0 out of 10

    Antigravity App v2.29.0: Jupyter notebook viewer, redesigned Automations, voice mode, and remote agents (opens in a new tab)

    sweep: Google Antigravity

    Worth a look for one line: remote agents move the loop off your machine into a cloud project. Voice, notebooks and Automations are UI. Sandbox and tool access are unstated.

    alsoantigravity.google (opens in a new tab)

    why 6.0

    Changelog adds remote cloud agent execution, which changes where the agent loop runs; the headline is mostly UI features, so the mechanism is only partly visible.

    relevance 6/10 · novelty 6/10

  4. Score 5.6 out of 10

    My least favorite phrase in AI security right now is "out of scope." Agents still install the archived Puppeteer MCP… (opens in a new tab)

    X (web)@eric_m_freeman

    Fair point: agents recall an archived MCP server from training data, and that server has a known injection-to-RCE path. Blocking it at a hook is a check the model cannot argue with. Law 4.

    why 5.6

    Concrete security failure: agents install archived MCP server with injection-to-RCE; proposes hook-based blocking.

    relevance 6/10 · novelty 5/10

Nothing of this kind on this day.