We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
🔥 TOP SIGNAL
The alpha is shifting from “ask the agent to write code” to “give it a standing verification lane.” Theo’s review of Sashiko describes a self-contained Linux-kernel review agent that ingests mailing-list or local-git patches; Sashiko’s reported test found 53.6% of bugs in the unfiltered last 1,000 upstream commits with fix tags using Gemini 3.1 Pro, while the review notes that its output is probabilistic. Theo’s boundary is the useful one: use AI to review existing code, build test tooling, and write throwaway tests, but keep human review before merge.
⚡ TRY THIS
Run an AI verification lane before human merge. For each PR, have the agent review the diff, generate targeted or throwaway tests for assumptions, run them, and return a fix list; re-run after changes, then read the final code yourself. Theo describes patch bots giving submitters feedback before a human maintainer would realistically read the change, with failed checks telling the maintainer to defer review while the submitter iterates.
Clear compile friction before asking for a fix. Start with Simon Willison’s prompts:
Clone x/y from GitHub and tell me how Z works, thencheckout and build Xand come back ten minutes later. He says this makes codebase exploration routine and turns compilation into a zero-time investment; @mitsuhiko reports serious progress on a stale serde issue in under four hours versus a month previously, while calling the result “slop.” The branch targeted issues he had opened almost eight years earlier.Automate fork upkeep with a verify-before-replace loop. Use David Crawshaw’s exact prompt:
Set up a nightly cron job that executes the prompt: fetch upstream changes to theand rebase all local changes on top of upstream. Check that the software works as intended and replace the current version. Simon quotes it as a pattern for open-source devtools; the critical clause is “Check that the software works as intended” before replacement.
Measure your agent’s baseline context overhead. Send
Reply with "hi"before a real task and inspect the context panel. Kent C. Dodds’ example shows 8% overall usage—about 20.8K of 256K tokens—with system prompt, tools, rules, skills, MCP, subagents, and conversation broken out. Use that baseline to trim global instructions or integrations before a long run.
📡 WHAT SHIPPED
Cursor + Google Workspace plugins. Cursor’s official changelog says coding agents can read, write, and act across Gmail, Drive, Calendar, Docs, and Sheets; available actions include searching and drafting mail, updating calendar events and finding free time, and editing Docs and Sheets. Install from the Marketplace or Cursor’s Customize page.
Cursor cloud-agent efficiency update. Cursor says cloud agents are now 20–30% more token-efficient and 80% more efficient on computer-use runs after improvements to MCPs, skills, and computer use. Treat those as vendor-reported numbers, but they directly target longer delegated runs staying within budget.
Frog. The new automated friction logger turns agent papercuts that would otherwise be silently worked around into tracked issues automatically. The useful pattern is simple: make the workaround produce backlog instead of disappearing.
Qwen 3.8 Max is a cheap open-weight coding-agent candidate. Matthew Berman describes the model as 2.4T parameters and relays a Terminal Bench score of 86.6 versus Fable’s 84.6, just under GPT-5.6 Sol; he also warns that benchmark numbers can be gamed and may not generalize. OpenRouter pricing is reported at $2/$6 per million input/output, versus $5/$30 for GPT-5.6 Sol and $10/$50 for Fable—but Qwen had not yet been tested on Artificial Analysis’s task-cost benchmark, so test per-task cost rather than routing on token price alone.
Model-upgrade regression signal. Steve Yegge says Gas Town worked brilliantly through Opus 4.6 but “fell apart at the seams” with Opus 4.7’s “just two more things” tic, which prevented convergence and left it “effectively burned down.” Pin model versions and run a canary workload before upgrading agent harnesses.
Synara licensing incident. Theo says Emanuele used Codex to auto-clone T3 Code’s features while claiming Synara was built “from scratch”; Emanuele apologized for changing the MIT license, said he had not understood its importance, and promised to restore it. Make license preservation and fork provenance acceptance checks for agent-generated projects.
🎬 GO DEEPER
Podcast clip — The Inference Engineering Masterclass, 00:01:26–00:05:40. Philip Kiely and Ali Taha walk through cache-aware routing for 200K-token coding or multi-turn-agent requests, disaggregated prefill/decode, traffic-specific speculative decoding, and when high-volume workloads justify dedicated deployments.
Video clip/project study — Sashiko walkthrough. Focus on the Linux-kernel-specific prompt and protocol, mailing-list/local-git ingestion, and the “AI review before human review” loop; it is a concrete design to borrow rather than another one-shot coding demo.
- Essay/project study — Gas Town and The Shape of Things to Come. Study the failure mode: a harness can be operationally sound on one model version and non-convergent on the next, so upgrade tests need to measure behavior, not just API compatibility.
Editorial take: The useful agent loop is now delegate → verify → capture friction → maintain; model upgrades and open-source provenance belong inside that control loop, not after it.