Vol. I · No. 65TUE, JUN 23, 2026
Archive

The Archive

Search the full wire by company, model, lab, or keyword. Every story we have ever aggregated.

Attack of the killer script kiddies

Last August, some of the best cybersecurity teams in the business gathered in Las Vegas to demonstrate the strength of their AI bug-finding systems at DARPA's Artificial Intelligence Cyber Challenge (AIxCC). The tools had scanned 54 million lines of actual software code that DARPA had injected with artificial flaws. The teams were capable enough to identify most of the artificial bugs, but their automated tools went beyond that - they found more than a dozen bugs that DARPA hadn't inserted at all. Even before the security earthquake that Anthropic delivered this month with Claude Mythos - the...

·

Anthropic hitting 40% enterprise share makes the "just add a fallback provider" advice weaker, not stronger

Menlo Ventures' enterprise survey put Anthropic at 40% of LLM spend, OpenAI at 27%. The takes I've seen are mostly about the leaderboard. The thing nobody's saying out loud: the standard agent-reliability advice ("don't depend on one provider, add a fallback") got harder to actually execute, not easier. When the split was closer to 50/30, both providers were realistic peers. You could run prod on one and have the other warm. Now most of us are running primarily on Claude — Sonnet for tool calls, Opus for harder stuff — and the "fallback" is a model we haven't tested against our actual prompt...

··

Anthropic Support is a joke

Rant on Anthropic Support I have two macbooks. One is an Air and the other is a Pro. On my Pro model the Claude Code stopped working inside the official anthropic application altogether. Whenever I would type a message, it would create a session w/ a summary of the name but wouldn't ever do anything. Just a blank screen. No error messages, nothing. I spent forever troubleshooting it, pulling logs, reinstalling, clearing cache, etc. to no avail Reached out to Anthropic, got their AI bot, once it couldn't solve my issue it forwarded my message to a human. It took over a month to get a...

··

Found 48 Vulnerabilities in Open Source Projects During Live Testing with Claude Opus 4.6

https://preview.redd.it/g98j5txd7sxg1.png?width=936&format=png&auto=webp&s=df75bc132f57cc14ba04cdd06257ba997b9bbb0b Ran a loop where each round runs Claude in a sandboxed Docker container with a fresh context window. The key difference is that the goal is **objective and verifiable.**  When I ran it on a repo, I noticed that during rounds 1-2, it found several independent low-risk vulnerabilities, but then, from round 3 onward, it started chaining them into critical exploits. This emergent behavior makes it very interesting.

··

4.6>4.7

Reddit discussion comparing Claude 4.6 vs 4.7 thinking modes (extended vs adaptive) with reference to prior posts.

··

I vibe reverse-engineered my Divoom MiniToo's Bluetooth protocol to make a physical Claude Code status indicator

I’ve been playing with a Divoom MiniToo and ended up reverse-engineering enough of its Bluetooth protocol to use it as a physical Claude Code status indicator. Pretty much vibe reverse-engineering: I gave the Opus model the Android APK file to study, gently encouraged it to use jadx, and then kept letting it know whenever it crashed the device. The repo, if you're interested: [https://github.com/bugzmanov/divoom-minitoo](https://github.com/bugzmanov/divoom-minitoo) macOS only for now, but porting to other OSes should be easy The repo also includes protocol notes, a macOS Bluetooth daemon...

··

FTW - is anyone else facing this?

..that too while the task was in b/w - Claude is disappointing me these days... For context: I'm just repromtping something that was generated - it was simply to edit the content

··

When your data is so bad...

Reddit discussion about data quality issues affecting Claude outputs; lacks technical specificity.

··
30 matches