Quality comes from checks the agent can run

Addy Osmani made the clearest argument this period. He says agents write better code "at scale" because they make checking cheap. Tests, benchmarks, specs and real end-to-end runs used to be what made good code expensive, and now you can ask an agent for them. So the job shifts from "review every line" to "build loops the agent can run itself" @addyosmani. He also says to make taste compound: when the agent gets something wrong, write the fix into shared config, a hook or a test so it doesn't happen twice. You still own what ships, but you review evidence as well as diffs @addyosmani.

He was responding to a complaint that asking Claude to review code is a slot machine that finds new bugs every time. His fix for that has three steps @addyosmani:

1. Define "done" before review starts. Without that, a reviewer (human or agent) can always find something to improve.
2. Give Claude checks it can run, such as bash commands, tests or clicking through the app in a browser, and require them to pass before it says it's finished.
3. When nothing blocks, merge and ship.

Salvatore Sanfilippo (antirez) shows the same idea on hardware, in a video where Opus 5.5 reworks his RP2040 ZX Spectrum emulator and adds a Commodore 64 emulator. The video is in Italian. Several steps are worth copying:

• Make a separate scratch copy first. Before porting his C64 emulator into the device project, he had the agent make a gitignored, uncommitted copy inside the repo. It converted that copy to instruction-at-a-time execution on its own and reported back before any integration. He warned it would get tangled if it converted and ported at the same time Salvatore Sanfilippo.
• Use the old implementation as the oracle. The agent ran the old cycle-accurate emulator and the new one side by side, requiring matching images and registers. After 10,000 frames the output was still bit-identical Salvatore Sanfilippo.
• Measure, then redesign. The faithful port ran at about 10% of real speed. The bottleneck was the VIC video chip Salvatore Sanfilippo. He told the agent to capture register writes and render frames from them instead of emulating the chip cycle by cycle Salvatore Sanfilippo. The result runs Spectrum and C64 in one device at 400 MHz, including timing-heavy C64 demos at 50 FPS with sound Salvatore Sanfilippo.
• Give the agent instrumentation and inputs. It simulated key presses itself Salvatore Sanfilippo. He says its first port worked on the device first try Salvatore Sanfilippo, and its instrumentation checked for delays, dropped frames and audio problems Salvatore Sanfilippo. His C64 emulator also exposes a direct API for stepping, debugging and grabbing frames, which he prefers to an MCP layer he sees as adding friction Salvatore Sanfilippo.

Separately, MaciekCodes reports that his own coding agent, "a 'while loop' and a few tools," improved itself quickly @MaciekCodes.

GPT-6.1 Sol: bigger default context in Codex, and plan math

Tibo (OpenAI) says GPT-6.1 Sol's default context in Codex & Work went from 272k to 500k, about 80% more. The aim is fewer compactions and better handling of long, nuance-heavy tasks. You can set it higher or lower, up to Sol's 1M maximum @thsottiaux. Subscription usage of Sol carries no long-context fees @thsottiaux.

Theo thinks the default speed was raised too much and is now barely slower than "fast" @theo. He estimates he could use Sol Ultrafast as his main model on the $500 plan and only just hit his limits @theo. That figure is his total usage (583/week), and it leaves out his long-running ts-rust work @theo. He also built a dashboard that tracks Claude usage across his accounts to roughly predict how long his limits will last @theo.

Theo: judge models by cost per completed task

In a new video, Theo argues that per-token price is the wrong measure for agentic work. Token-hungry models can wipe out a low sticker price. For agentic dev work he says caching, reliability and token efficiency matter much more Theo - t3․gg. He says bills are rising because agents now run longer and finish bigger tasks Theo - t3․gg. He favors GLM 5.3 Flash for real-world agentic work, citing its vision, tool calls and long-running work Theo - t3․gg.

The sponsored segment of the video (Railway) still describes a usable pattern. On his Lakebed project, agents set up production, staging and per-PR environments for him. Claude or Codex connects through Railway's MCP, spins up an environment, verifies a change, ships by merging to main, then checks on the environment afterward Theo - t3․gg.

For local compute limits, he moved ts-rust's build and test commands onto Blacksmith runners. Each thread still takes a while, but he is far less bottlenecked when running many in parallel @theo.

T3 Code nightly

Theo added a proper /goal flow with a visual callout to the T3 Code nightly @theo. A user showed off the new inline rendering in chat by asking the agent whether a monitor mount would clamp onto their desk @aflekkas_. Theo says he hadn't expected the feature to be so useful @theo. For hazy features he still uses Matt's "grilling" skill, noting that modern models are good at asking questions @theo.

Smaller notes

• Riley Brown shared a grokbot-webhook skill. Claude Code hands X/Twitter research to GrokBot, waits for the answer, then continues with the task @rileybrown. He says it works with any agent, including Codex @rileybrown.
• Kent C. Dodds shared the Kody v2026.10.11 release (release notes). Cron jobs, webhooks, subscriptions and inbound email now run with the permissions of whoever enabled them, checked live on every run, with no fallback to the org Owner @kodykoala. His caption: "This is what 122 PRs in one day looks like" @kentcdodds.
• Armin Ronacher says no single agent runtime wins. VMs, sandboxes, durable objects or a plain JavaScript interpreter each fit different situations @mitsuhiko.