The Wire / 2026-08-20
Three days, one migration told twice: OpenAI says Asana cleared five years of test-framework work in two weeks with Codex, and Pragmatic Engineer asks what agents actually changed about migrations. Around it, a sandbox measured rather than launched and an argument for keeping a privileged core.
-
The Pulse: We need to talk about migrations with AI
Orosz on why some migrations sat untouched for years: the serial step was human attention, and agents changed that bottleneck without changing whether the result is right. Asana's test-framework move, told by OpenAI below, is one of his cases. Read his framing before the vendor's number.
-
The /wayfinder Skill: Navigating the Fog of War of Planning
Matt Pocock on a skill for the moment the next step is unclear. It sits on top of Claude Code rather than inside it, which is where much of the new planning help is being built. A skill is an instruction the model may follow, not a control the harness enforces.
-
Asana cleared 5 years of engineering work in 2 weeks with Codex
The vendor's telling. "Five years in two weeks" is OpenAI's framing, and we have not seen how the five years were counted. The migration may well have happened; the compression ratio is a claim without a method. Do not quote it as a benchmark.
-
smolmachines / smolvm as a sandbox for untrusted Python and JavaScript
Willison puts a fast sandbox through its paces for running untrusted Python and JavaScript. It is a practitioner's measurement, not a launch post, which makes it a useful reference if you are choosing where agent-written code runs. The results are his, on his workloads.
-
Quoting Jeremy Morrell
Extensible software with a solid core and a sandboxed extension layer, cheaper to author because of LLMs. It is the opposite design from DeepSeek Harness, which put its approval gate in a plugin. If you are choosing between the two shapes, the question is which code you are willing to let an extension replace.
-
Recovering Encrypted LLM Reasoning Traces
Rehberger reproduces a paper on recovering encrypted reasoning traces from proprietary APIs. If it holds, a trace a vendor encrypts is not a trace you can assume stays private. The reproduction is his; we have not run it.