We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
🔥 TOP SIGNAL
CI, not inference, is becoming the thing that slows agent-heavy teams down. Altimor (Lindy) says CI is "the top bottleneck of every engineering team I talk to" and calls Lindy's own CI spend "stratospheric" . Two responses are worth comparing. Peter Steinberger plans to "let codex decide which tests actually need to run and drastically nix CI and run tests hourly" . Geoffrey Huntley's answer is nix-build on big Hetzner bare-metal boxes set up as trusted remote builders for your agent, with traditional CI kept only for complex integration and pre-release regression tests. He points to Hydra as the state of the art . Neither has published results yet: Steinberger's is a plan and Huntley's is a recommendation.
⚡ TRY THIS
Stop being the "meat proxy" (DHH, Rails World panel). If you're copying error messages between agents, "consider just letting the agent read the error messages directly" . He treats agent PRs and issues as suggestions: if he likes one, "my agent will pick the slop apart and return with a beautiful implementation" . He says agent-opened PRs and issues are better than the average human ones on any repo he has managed . On how much autonomy to give, his answer is "as much as their competence warrants." Measure that by whether the last PR was handled correctly, and check in less as trust builds . Matz's version: 20 issues and PRs came in within an hour before the keynote. He asked the Claude app on his phone to address them, and by the end of the talk it had resolved 12 .
Make your internal tools agent-native (Riley Brown). He listed the features he actually used across Notion, My Mind, Typefully and Google Drive, then asked Claude for "an app that does all those things that looks really good." It took about 20 prompts, and he tested it with several video-editor agencies . The useful part: a Claude Code skill called "native note" writes directly to the app's database. "Add it to native note" creates a linked script thread, so the agent uses the same software the team does .
Property-fuzz your agent's output all the way down to I/O (Huntley). He "vibed up" a setup that uses bombadil to autonomously explore web and terminal apps with property-based testing, asserting properties on side effects in databases, the filesystem and systemd units. It's packaged as deterministic NixOS machine tests that take a seed, so you can fan verification out across a fleet with Hydra .
Use a constrained machine as the performance target (DHH). Keep a ten-year-old "potato PC," put your agents to work inside it, "and watch the weight drop" .
📡 WHAT SHIPPED
Why Opus 5.5's limits feel much bigger (Theo's math). Claude Code subscriptions allow Fable to use only 50% of the usage, and Opus 5.5 High costs less than half as much as Fable 5.1 High. Theo puts Fable 5.1 High → Opus 5.5 High at about 4.3× more usable limits, and his own switch from Fable 5.1 xhigh at about 6.6× . Addy Osmani's official-side numbers: limits go about 25% further than on Opus 5, cache reads cost 60% less, and output is 30% faster (cost post) . Riley Brown hasn't hit a limit in five days. He grants Astra may be better "at a good amount of things," but says it's slower and much more expensive .
Antigravity 2.0 agent teams (Kevin Hou, Google DeepMind). The agent manager is now a separate app from the IDE .
/teamwork(public preview) starts a lead agent that asks clarifying questions, then creates specialized subagents. The lead can pick a different model for each subagent . Hou says Gemini 3.5 Flash is "really good at leading teams," and faster and cheaper . Sidecars are long-running plugin processes that listen for SMS, webhooks, cron or GitHub PRs. Hou said the spec would be released "later this summer" . Their showcase run built an OS kernel that runs Doom: 93 subagents, 12 hours, 15,000 requests, 2B tokens, under $1,000. Hou says it's not something they'd do every day .Computer use: people are preferring Codex. @jtaby: "insane how much worse computer use is in claude vs codex" . Riley Brown: "Codex computer use is absurd. Especially on Mac" . These are impressions, with no tasks or benchmarks given.
jevgrep (repo). A research-agent CLI from @dzhng built on typesafe's jev. It claims a 40% cut in coding-agent cost, "verified on SWE-bench." Install its built-in skill so your agent uses
jgfor context collection . The claim comes from the tool's author and hasn't been independently checked.ttfx sequel: people rewrite the agent's code too. Daniel Collin has a WIP Rust rewrite of Opus's assembly port with AVX-512/AVX2/SSE2/Neon paths. He reports it's about 10.7× faster than the original Rust and 1.25× faster than the asm on average (PR #44) . DHH: "I have zero allegiance to whatever code my agents wrote" .
Security caution. @_mattata's project to audit every line of the top 1,000 GitHub repos in under 30 days for $100 is "nearing completion" . Huntley's conclusion is that with LLM red-teaming, putting source on GitHub now reduces its security . No findings have been published.
A personal-agent failure worth studying. Simon Willison quoted a Muse agent admitting that its auto-reply told a buyer "Yep I'm here!" when its user wasn't there. The buyer left a negative rating, and the agent then offered to stop making claims it can't verify . Lesson: don't let an agent assert real-world state it can't check.
🎬 GO DEEPER
- Kevin Hou on automating side-by-side evals with subagents. Researchers load a skills file and ask about an eval in plain language. The agent computes the control/experiment delta, a research subagent proposes about 100 hypotheses, one subagent investigates each in parallel, and the result is a report with a generated UI. Hou says 90% of the workflow is automated and it takes minutes instead of Jupyter "elbow grease" .
- DHH and Matz on agent PRs, "meat proxies," and calibrating trust. A short stretch covering the whole "suggestions, not implementations" stance and Matz's 12 issues fixed from his phone.
- Riley Brown's agent-native internal app demo. The skill that writes to the app's database is the part to copy.
- Huntley, "the eighteen-month recap". Agents are "just a while loop, and Ralph is a while loop on a while loop" . His free 300-line workshop has you build your own Cursor/Copilot/Codex . Separately, he says he doesn't pre-install skills or cram markdown into context: "Stop chasing LLM prompt fairies and instead focus on the craft" .
Editorial take: Opus 5.5's cheaper limits make generating code close to free, so the costs now sit in CI, test selection, and deciding how far to trust agent output.