curated · 2026-07-11

This isn't a vague "AI is dangerous" warning. Cambridge researcher Antonia Jülich conducted 57 interviews and got first-hand accounts from 27 former Boko Haram members. Both factions set up dedicated AI units—they'd gather top people in a room and use a projector to teach how the tools work. ISIS has been running prompt engineering and jailbreak training for commanders since 2023. Specific uses: attack planning, building more powerful explosives, weapons maintenance, operational security. The wildest case: the ISWAP faction used AI to replicate motorcycle jump techniques from a movie to clear trenches. Eighteen fighters died in training; eight made the jump. Jülich's warning is worth taking seriously. Current use is conventional, but former members said the group previously considered mass-casualty weapons, so the risk of them seeking AI help for chemical and biological weapons shouldn't be dismissed. The post doesn't give per-model misuse counts or success rates, and doesn't detail where safety filters failed. But Anthropic recently admitted jailbreaks likely can't be fully eliminated. Researchers also note that chatbots like ChatGPT and Claude mostly make existing knowledge easier to find—the bigger worry is potential misuse of specialized AI systems in the life sciences.

This caught my eye because the eval design is tougher than typical benchmarks: specialists got unlimited time and web access to write answers, then other doctors blind-rated them across accuracy, communication, completeness, instruction-following, and health-decision helpfulness—20,000 scores total. All GPT-5.6 models significantly outperformed doctors, and doctors found fewer flaws in GPT-5.6 answers than in peer-written ones. The smallest variant, GPT-5.6 Luna, beat the highest-reasoning GPT-5.5 at its lowest reasoning strength while costing 25× less—that cost-performance ratio matters a lot in clinical settings. But right now we only have Sam Altman's tweet and a snippet; the post doesn't disclose the disease mix or specialist composition tested. I'd discount this a bit until we see whether the task set skews narrow or common-case.

The numbers are what make this worth clicking: 11 days, 1M+ lines, $165K to port an entire JS runtime from Zig to Rust. Bun was acquired by Anthropic in December 2025, so the API bill was effectively an internal transfer. The motivation is practical—Zig's memory errors and crashes were hard to fix, and Rust catches many at compile time. v1.4.0 shipped as a canary with 128 bugs fixed and a 2–5% speedup. Sumner estimates a human team would've needed a year. I'd discount the 1M-line figure a bit—that's total generation, not what landed in main. The post doesn't detail how much review and coordination the 64 parallel instances required. And this is Anthropic's own model working on Anthropic's own acquisition; nobody else gets this cost structure. But the direction is solid: LLMs handling a language migration with clear translation rules, especially Zig to Rust, is a genuinely good fit.

This one's worth opening because the failure mode is painfully classic: not a model going rogue, but a $HOME variable expansion error in shell that turned a cleanup task into rm -rf /Users/mattsdevbox. Matt Shumer gave it Full Access, let a subagent run autonomously for a while, and hit the trifecta—top models still trip on path expansion details, full permissions plus long autonomy chains turn small mistakes into disasters, and safety baselines vary wildly across providers. His "trust Anthropic's Fable 1000x more" line is emotional, but it points to something real: when an agent touches your local filesystem, permission isolation and rollback mechanisms matter more than model intelligence. We only have his account so far, no full logs, so I'd discount the specifics a bit—but the core lesson doesn't need them. Don't give agents Full Access, and don't let them operate directly on $HOME.