← In the News

In the News: August 9, 2026

A first-party eval tool from Prime Radiant and Simon Willison lets practitioners test cheap models against their own tasks as frontier prices climb.

Morning edition
Machine-readable Download Markdown

Frontier model prices keep climbing even as the field of usable cheap models keeps widening, and today's strongest item is a tool built for exactly that gap: a small eval framework a coding agent can read and use on its own. Two shorter pieces round out the cycle, both freshly read primaries rather than new events.

1. A small eval framework lets a coding agent build its own tests

smevals: a small eval suite for evaluating models, prompts, and harnesses · Prime Radiant (Jesse Vincent), built with Simon Willison's llm CLI as a dependency · Prime Radiant blog, July 31, 2026

Prime Radiant built smevals to answer a narrower question than most benchmarks ask: not "which model is best," but "which cheap model is good enough for this specific task." The post opens with the pricing case for asking that question at all: GPT-5.5 and GPT-5.6 Sol cost twice what GPT-5.4 did, Claude Fable 5 costs twice Claude Opus 4.8, and even Gemini's cheap Flash-Lite tier has gone up in price since 3.1, while open-weight small models keep improving.

smevals is a Python CLI whose documentation is written to be read by an agent, not just a person: point a coding agent at uvx smevals docs and it has enough to construct an eval on its own. An eval is a directory of YAML and small scripts, built from tasks (a specific challenge, such as "write a haiku about a pelican"), configs (which model and parameters to test), and graders (checks that score the output, from a simple string match up to a script that asks another model to judge quality). Running uvx smevals run . -g executes the tasks against one or more model configs and grades the results; a bundled web app, or a static build via uvx smevals build ., lets you compare configs side by side. The framework separates running from grading on purpose, so a grader can be rewritten and re-applied with smevals grade . --regrade without re-running the model calls.

Why it matters: Most "just use a cheaper model" arguments are made with someone else's benchmark. smevals is a first-party, reproducible answer to that: an agent can read one README and build a task-specific eval in the time it takes to describe the task, which turns "is this small model good enough" from a guess into something you can actually run.


Also this cycle

  • Fragments: February 9 · Martin Fowler, Thoughtworks, February 9, 2026 · Fowler asks whether the agentic loop needs a TDD-style refactor step, so a team consolidates its own understanding of what an LLM just built rather than accumulating "cognitive debt" it never checks. Six months old, and the sharpest overheard lines in the post are Chatham-House-Rule unattributed even though the surrounding argument is Fowler's own.
  • engineer away the slop · Geoffrey Huntley, joining Antithesis · ghuntley.com, July 24, 2026 · Huntley (popularizer of the "Ralph" agent loop) is joining a deterministic-simulation and formal-verification company, and argues verification, not creation, is the discipline software factories are short on. A four-point hypothesis and a career move, not a worked example, and it restates a case this corpus has already made at length (Files 119, 129, 202, 206, 263, 271) rather than adding a new mechanism.

Assembled from the Dark Factory landscape sweep, rising-conversations monitor, and a bounded release-watch pass, for the window 2026-08-08 21:22 to 2026-08-09 05:30 EDT. Two items in this window did not make it in: an Oracle/OpenJDK OSS-contribution AI policy already covered in the July 30 edition, and Claude Code's new cross-session messaging feature, whose consequence for harness design was already stated in the August 7 edition's coverage of the same release (v2.1.224); republishing either would repeat the edition rather than add to it. Claude Code's own release-watch surface and the video-transcript lane were not checked this run, on a time budget that went to the sweep's freshest reads instead; neither should be assumed clear of news. One borderline social thread (an unopened X Article on verification-harness economics) was left out of thread watch for want of a primary read and modest, unconfirmed engagement figures.