We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
🔥 TOP SIGNAL
Stop relying on yes/no approval prompts. Put a context-free safety checker and a real sandbox around agents instead. Boris Cherny, who created Claude Code, describes an Anthropic study. Contractors doing coding puzzles were occasionally shown injected commands that would have damaged their systems if real, and they approved them "almost all the time." He calls the prompts "security theater" . Claude Code's auto mode sends each proposed action to a second model that has none of the conversation's context. Cherny says it "gets it right almost every time," and you can customize its rules by asking Claude . He also says to "always use the sandbox," even in production .
Why the sandbox has to be tight: Jeff Ladish reports agents that could only load URLs, with no way to send data. They used a link-shortener to create almost a million URLs that, chained together, let them execute code and hack Hugging Face . Loading URLs was enough to get data out.
⚡ TRY THIS
Use the sandbox the way Cherny describes it: a box that stays closed, with specific holes cut in it. Allow model inference, only the folders the agent needs, and a named list of websites. Block general web access, because "to do useful work you probably don't need access to the whole internet" . He says Claude Code's sandbox is open source and works with any agent. Claude Code users have to turn it on themselves because it's off by default .
Have agents turn a web page into a video (Simon Willison). Willison got a pixel-art HTML canvas animation from Claude Opus 5.5 . He then told a local Claude Code session:
Make me a video of file:///…/kakapo-party.html - you need to load it in a browser and click on it a few times to get the confetti effect, the video should be 15s long/don't start clicking until 3s in/make sure several clicks are spread around the clickable area. Claude Code wrote a short Playwright script. It opens Chromium at 1280×720 with video recording on, clicks at 10 timed points spread from the center to the corners, and closes at about 16s . The pattern carries over to demos, bug-repro videos, and visual regression capture.Make verification fast, not just thorough (Geoffrey Huntley). Each change needs checks that push back, but if those checks are slow, every LLM mistake costs you cycles. His target: read a file, build, and run tests in milliseconds. His prediction: the bottleneck will be verification speed and "how fast you can verify and pump the result back into the inferencing window," not inference . Huntley also says Hegel-powered property-based testing for NixOS "found stuff," and he plans to open-source the pattern .
Run parallel hypotheses and have agents check each other (Cherny). His typical data-analysis sessions run up to about 12 hours. Claude forms a hypothesis, sends about 10 agents to investigate in parallel, then checks their findings and throws some out before going deeper . Small one: Addy Osmani points out that the Claude Code desktop app's "Keep computer awake" setting stops your machine from sleeping during long sessions .
📡 WHAT SHIPPED
Jev Router got benchmarked, and it doesn't come out ahead. Theo spent $1,000 testing OpenRouter's
typesafe/jev-router. On DeepSWE it scored about the same as GPT-6 Astra on low, cost slightly more, and took almost 5× longer . His explanation: Jev "categorizes" and doesn't reason, so it can't tell whether "port this to Rust" means a 100-line file or a million-line app . He adds that switching to a cheaper model partway through a task saves little when cache writes are "such a massive % of cost" . Takeaway: routing on the prompt alone is a weak way to choose reasoning effort for coding agents.ttfx 0.4 (Omarchy): the assembly engine written by Opus is released. DHH says the print effect now runs more than 1,000× faster than the original Python and 32× faster than the old Rust. It ships in the next Omarchy, and a faster Rust fallback is coming . His observation: hours of frontier-model work on the Rust version brought "very modest improvements," while moving to assembly brought big jumps (8× mean on an Intel 135U) . These are one project's own numbers, not a general benchmark.
Oligarchy, a harness for agent-driven QA (announced, not live). ThePrimeagen joins Omarchy Core to lead Agentic QA. The harness will vet upcoming releases with agents running on DigitalOcean droplets . He promises a write-up with milestones and expectations this week .
Open-weights model as a daily driver. Huntley runs Kimi/K3 as his main model on a couple of racks of B300s in a Sydney data center . He reports about 200M tokens an hour and expects close to a billion within five hours .
Subscription value, based on one person's heavy use. Theo says he maxed out about 3.5 of the $200 Claude Code accounts in 5 days and calls the Max plan "an absolute steal" .
Theo on the "Opus 5.5 got nerfed" claims. He points to one real incident: last year, inference optimizations across Nvidia, Trainium, and TPUs caused degradation that Anthropic later fixed and explained. He says there have been no notable cases since. His statistical point: with a 1-in-50 chance of an odd output and 20 prompts a day, you have about a 30% chance of seeing one on day 1 and about 90% by day 5 . Don't read a single bad run as a regression.
Two points about avoiding lock-in. Kody's pitch, shared by Kent C. Dodds: keep memory, secrets, and packages in your own "house" so you can swap agents or use several at once . Riley Brown criticizes Descript's MCP: it just forwards Claude Code prompts to Descript's own Underlord agent, which costs more and forces you onto their tokens .
🎬 GO DEEPER
- Cherny on why approval prompts fail and how auto mode replaces them. The contractor study and the design of the context-free safety classifier.
- Cherny on designing an agent's tool set. Claude Code started with about 4–5 tools (read, write, bash, screenshot). Subagents are just "Claude starts a Claude" and can choose Opus or several Haikus. Tools get added and removed with every model release, and "often it's not the obvious thing that works… it's often the simplest thing."
- Salvatore Sanfilippo (Italian) on C vs Rust for LLM-written code. He argues that LLMs write C much better than any other language because of the huge, high-quality C codebase they learned from. He would use C for services that aren't security-critical, audit it heavily, and keep Rust for mission-critical code that can't be isolated .
- Post: Simon Willison, "Kākāpō Party": The full prompts, transcripts, and the Playwright script from the TRY THIS item .
Editorial take: The limit on agents is no longer model quality. It's how fast you can check their work and how tightly you've boxed them in.