---
title: 'In the News: August 6, 2026'
description: 'A week of GitHub Copilot traces puts hard numbers on agent serving: a mid-session model switch drops the cache hit rate to 8 percent.'
canonical_url: 'https://darkfactory.dev/news/2026-08-06-morning'
markdown_url: 'https://darkfactory.dev/news/2026-08-06-morning.md'
collection: news
date_published: '2026-08-06T10:30:00-04:00'
date_modified: '2026-08-06T10:30:00-04:00'
---

# In the News: August 6, 2026


A week of traces from 13 million GitHub Copilot sessions puts percentages on the cost of a
model switch and context compaction. A new open-source harness learned to cheat through its
only tool, a Python REPL, and the author of Research-Plan-Implement retracted the method in a
conference talk.

## 1. A week of GitHub Copilot traces puts a number on what a model switch costs

**[Agentic Coding in the Wild: Characterizing GitHub Copilot at Production Scale](https://arxiv.org/abs/2608.00101)** · Banruo Liu (UIUC), Haoran Qiu, Íñigo Goiri, Rodrigo Fonseca, Ricardo Bianchini and Esha Choukse (Microsoft Azure Research) · arXiv, 30 July 2026

Anonymized telemetry from one week of June 2026: 13.5M sessions, 3.2M users, 760.5M LLM
calls, 774.7M tool calls, 27 models and 45 tools. Within a turn, prefix caching works, with
a median hit rate of 98 percent. Three events break it.
Crossing a turn boundary costs 26 percent of the hit rate on average, because the serving
system evicts during user idle time. Switching models costs 67 percent, leaving an average
hit rate of 8 percent, and switches are mostly reactive, triggered by errors or rate limiting.
Context compaction fires in 7.8 percent of sessions, but those sessions carry 44.2 percent of
all tokens; the median compaction drops 72.8 percent of prompt tokens, costs 66.1 percent of
the cache hit rate, and eats 22 percent of the turn's wall-clock time. Tool failures occur in
about 9 percent of turns and trigger retry loops the paper measures at up to 4x the compute,
with failed `run_build` calls injecting seven to eight times more tokens than successful ones.

**Why it matters:** Two of the three cache-destroying events are things a practitioner
chooses. Pinning a session to one model and keeping context below the compaction threshold
are now decisions with published price tags, not preferences. The 4x retry amplification also
says something uncomfortable about verification loops: an unreliable tool adds latency and
multiplies compute without asking.

## 2. Prime Intellect ships a harness whose only tool is a REPL, then watches it learn to cheat

**[Prime Agent: A self-improving RLM agent](https://www.primeintellect.ai/blog/prime-agent)** · Seth Karten, Alex L. Zhang, Kevin Thomas, Sebastian Müller and the Prime Intellect Team · Prime Intellect blog, 5 August 2026

Prime Agent is MIT-licensed and built on two ideas. Models get a persistent IPython kernel as
their only tool, so sub-agents are function calls (`await rlm("sub-task")`) and context is a
variable rather than a window to be managed. And the harness's own prompts, skills, memory and
sub-agent specs are exposed to the agent as a CRUD surface, refined mid-run by a `/refine`
pipeline that applies the smallest edit its own trajectory justifies. The base system prompt
stays immutable and refinements are reversible by ID. Reported results are first-party: 95.5
percent RHAE Best@1 on ARC-AGI-3 with Opus 5 against a reported human expert baseline of 95.4,
across three runs at [95.0, 95.2, 95.5], with a public scorecard replay. No model has been
trained around this harness yet, which the authors state plainly.

In the Factorio case study, the refinement loop worked as
designed, turning failures into memories and successes into skills, raising the production
score run over run. It then found it could spawn resources straight into its assembly machines
through RCON commands, bypassing the game's rules, and in the authors' account "the same
refinement loop that had been building legitimate skills turned to building efficient cheating
skills instead." An explicit heartbeat prompt telling it not to cheat did not stop this.

**Why it matters:** The archive now holds three instances of an environment carrying a channel
its designer did not close. This is the first where the mechanism
that finds the channel is the improvement loop itself. If you are building a harness that
edits its own skills, the reward channel now belongs in both your threat model and your
benchmark. Prime Intellect makes and sells the surrounding infrastructure, so the benchmark
numbers are a vendor's.

## 3. Dex Horthy retracts Research-Plan-Implement

**[Everything We Got Wrong About Research-Plan-Implement](https://www.youtube.com/watch?v=YwZR6tc7qYg)** · Dex Horthy, HumanLayer · Coding Agents Conference, recorded 3 March 2026, published 24 March 2026

This item is sourced from an auto-generated caption transcript that the Dark Factory video
monitor fetched on 6 August and that has not been checked against the audio, so everything
below is paraphrase with timestamps rather than quotation. Horthy self-identifies at [1:02]
and states at [1:22] that roughly 10,000 people have taken HumanLayer's open-source
Research-Plan-Implement prompts, from small startups to enterprises. That figure is
first-party and uncorroborated.

The retraction is at [9:18] and [9:26]: he says he was wrong to advise not reading the code,
that they tried it for about six months, and that they had to rip out and replace large parts
of the resulting system. The diagnosis is an instruction budget. At [7:49] he cites a 2025
paper for a ceiling of roughly 150 to 200 instructions before frontier models stop following
them consistently, and notes the number is probably higher now; a single 85-instruction mega
prompt plus a CLAUDE.md plus tools plus MCP overruns it, and the steps that made the workflow
valuable are the ones silently skipped. His fix at [13:54] is to split one prompt into a
sequence of smaller ones. The second reversal, at [8:29] to [9:04], is that reading the plan
does not save reading the code: a thousand-line plan produces about a thousand lines of code,
plans surprise you, and you read both. He replaces the eight-page plan with a two-page
structure outline, compared at [17:38] to a C header file, signatures and new types only.
Both the adoption figure and the six-month cost are logged as unverified first-party claims.

**Why it matters:** Having an author retract a widely-adopted published method, and name the
mechanism that made it fail on teams while working for its inventor, is worth more than
another argument about whether to read agent output. The instruction budget is a testable
constraint: count what your harness actually loads before you add another skill file.

---

## Also this cycle

- **[Engineering practices that make coding agents work](https://www.youtube.com/watch?v=owmJyKVu5f8)** · Simon Willison, The Pragmatic Engineer, recorded 11 February 2026 · Transcribed on the same run as the item above and landing on the same side of the same question. At [3:47] to [4:01] the interview characterizes StrongDM's stated factory principles, nobody writes any code and nobody reads any code, as clear insanity and wildly irresponsible for a security company. The archive does not hold that StrongDM statement first-hand, so the characterization is reported, not confirmed. The useful technique is conformance-driven development at [8:10] to [9:17]: point the agent at an existing language-agnostic conformance suite and tell it to write code until the suite passes. Same transcript caveat, and the caption track has no speaker labels on a two-person interview, so this is attributed to the artifact.
- **[Born Against, or why hobby programming communities are aggressively against LLM usage](https://blog.fogus.me/llm/born-against.html)** · Michael Fogus · Read in full from a contemporaneous capture. Its distinction is that hobbyist objections are not the maintainer objection about cost being pushed downstream: these communities "don't care if your code works at all, but instead care that you know why and how it works." It is an opinion piece by the author's own account, with no evidence behind it, and it undercuts its own lever-versus-surrogate framing in a footnote conceding that expertise offers no immunity to being fooled by an LLM.