🔥 TOP SIGNAL

The merge bottleneck is now verification. Elevate’s Agentic Code Quality argues that human review does not scale when agents produce enormous change volume; constraints in the harness, environment, and OS must decide whether each proposal is safe, correct, scoped, and useful, with back-pressure applied throughout the loop rather than only at the end. Elevate

Geoffrey Huntley’s concrete loop is already simple: prompt “impl xyz then commit/push,” have the agent run tests, then run AntithesisHQ’s “torture chamber” on the increment before commit/push/code review. @GeoffreyHuntley

⚡ TRY THIS

• Put the quality gate before the commit. Copy Huntley’s loop, then add checks matched to the risk: unit, property, and acceptance tests; mutation testing; architecture and lint rules; security policies; and CI deployment gates. The useful distinction is deterministic back-pressure—not asking a second model whether the first model’s code “looks good.” Elevate

• Turn AGENTS.md into an acceptance contract. A practical template from @reach_vb says to preserve the goal and constraints, finish authorized work and verify the actual result, ask only when a decision is materially ambiguous or risky, spawn subagents only for independent work, test observable behavior and the real interface, avoid unauthorized destructive actions, and report outcomes with evidence. @reach_vb Jediah Katz’s useful counterpoint: if the file needs constant edits to say “finish authorized work end to end,” the harness—not the markdown—is failing. @jediahkatz

• Keep parallel work bounded and disposable. Theo’s self-report says T3 Code lets him spin up, track, merge, and then close threads without getting lost; he reports roughly 20% more code but 10× more merges, followed by a session in which he built and merged a dozen PRs in four hours. Use one bounded task per thread, require an acceptance check before merge, and close the context when the work is done. Treat the productivity figures as vendor-adjacent field data, not a benchmark. @theo +2

• Use cloud agents for bounded maintenance while away from the desk. Debs O’Brien’s Cursor flow was: send one specific fix from the mobile app, wait for live updates, inspect the generated screenshots, then merge in the app or via GitHub. She used it for login and mobile-view work on a Playwright demo site—an async pattern for reviewable backlog items, not a license to delegate vague production changes. @debs_obrien

📡 WHAT SHIPPED

• Stateless MCP (2026.0728) is the real infrastructure release. Theo says the fifth MCP spec moves the protocol from bidirectional stateful connections to request/response, hardens authorization, graduates official extensions, and allows servers to run on serverless or edge infrastructure. Theo - t3․gg The key before/after is one HTTP request without session state instead of initialization plus session routing; the catch is that the new implementation is not backward-compatible, so verify the exact client and server versions before migrating. Theo - t3․gg

• T3 Code added a real usage surface. Its Nightly build now reports API cost and token usage across Claude Code and Codex, using the actual histories from all your machines rather than only activity inside T3 Code. That makes it possible to measure the burn rate of a multi-harness workflow before optimizing prompts or increasing concurrency. @theo

• Cross-harness model use got a policy signal. @thsottiaux says GPT-5.6 Sol can be used “pretty much anywhere,” including the CC harness, and says he reset limits for paid ChatGPT Work and Codex users. @thsottiaux Anthropic’s @bcherny separately says Anthropic does not ban people for using harnesses with other models and that a reported suspension was almost certainly triggered by a different account classifier. @bcherny

• Swyx’s “kill my SaaS” competition became a genuine demand signal. The live event accepts any coding agent and model under a $500 token-and-subscription cap, with the finish line extended to Wednesday; the follow-up reports more than 600 applications and 100 admissions. That is participation data, not yet evidence of clone quality. @swyx +1

🎬 GO DEEPER

• Video — Did Anthropic finally fix MCP?: Theo’s skeptical-to-optimistic walkthrough explains why stateful MCP created connection and process overhead, what the request/response model changes, and why the compatibility break matters. Theo - t3․gg

Editorial take: The durable agent advantage is shifting from generating more code to making every increment cheap to verify, easy to merge, and safe to discard. Elevate +1