Latest / Braid / When the Harness Modifies Itself

Transcript

When the Harness Modifies Itself · Braid

• 0:04
  At 11:39 AM Pacific today, Mario Zechner posted a screenshot that marks a threshold we all knew was coming but maybe hadn't quite processed.
• 0:13
  Claude Code — Anthropic's coding environment — is now modifying its own harness code.
• 0:19
  The agent is literally rewriting the infrastructure it runs on.
• 0:23
  Zechner's caption was dry: "i welcome claude code to the self-modifying harness game.
• 0:29
  baby steps."
• 0:42
  Not API usage — that was never in question.
• 0:45
  CLI usage.
• 0:45
  The kind where third-party tools hook into Claude's command-line interface to build coding agents.
• 0:52
  Except if you scroll back six weeks, Anthropic said the opposite.
• 0:56
  And three months before that, they said it was fine.
• 1:00
  The company that's now enabling self-modifying code can't maintain a consistent policy on whether developers are allowed to use their tools.
• 1:09
  Every major harness — Pi, OpenCode, OpenClaw — has built production systems on top of these interfaces.
• 1:16
  Thousands of developers are shipping code through tools that exist in a policy gray zone that changes quarterly.
• 1:24
  And now those tools are gaining the ability to modify themselves.
• 1:28
  Antirez weighed in with what might be the most pragmatic take of the day: "Maybe it does not matter what the different providers tell in a given moment since alternative coding agents and bots of all kinds at this point should be developed against frontier open weights models like Kimi K2.6 and similar, in order to be future proof."
• 1:53
  When your infrastructure provider can't decide if you're allowed to exist, and when that infrastructure is gaining autonomous self-modification capabilities, maybe the answer isn't to negotiate better terms.
• 2:07
  Maybe it's to find infrastructure you actually control.
• 2:11
  Speaking of infrastructure you control: Kimi just changed the game.
• 2:16
  K2.6 dropped on HuggingFace today, and the benchmarks are forcing everyone to reconsider what open source means for coding agents.
• 2:26
  66.7 percent on Terminal-Bench 2.0.
• 2:29
  For context, that's within two points of GPT-5.4 and better than Claude Opus 4.6.
• 2:36
  This is an open model you can run on your own hardware, modify however you want, and never worry about policy changes.
• 2:45
  But the raw benchmarks undersell what's happening.
• 2:49
  From Kimi's technical blog: "Kimi K2.6 successfully downloaded and deployed the Qwen3.5-0.8B model locally on a Mac.
• 2:58
  By implementing and optimizing model inference in Zig—a highly niche programming language—it demonstrated exceptional out-of-distribution generalization.
• 3:10
  Across 4,000+ tool calls, over 12 hours of continuous execution, and 14 iterations, Kimi K2.6 dramatically improved throughput from ~15 to ~193 tokens/sec."
• 3:24
  Four thousand tool calls.
• 3:26
  In Zig, a language maybe 0.01% of developers have even touched.
• 3:31
  Or this: "Kimi K2.6 autonomously overhauled exchange-core, an 8-year-old open-source financial matching engine.
• 3:40
  Over a 13-hour execution, the model iterated through 12 optimization strategies, initiating over 1,000 tool calls to precisely modify more than 4,000 lines of code."
• 4:01
  Result: 185 percent improvement in medium throughput, 133 percent in peak performance.
• 4:08
  On a system that was already optimized.
• 4:11
  BiggestBau5 in r/LocalLLaMA put it bluntly: "Opus 4.7 Max subscriber.
• 4:16
  Switching to Kimi 2.6." Their team was burning through the Max plan's limits daily, supplementing with Qwen 3.6 when they hit caps.
• 4:27
  Kimi K2.6 handles 85 percent of what Opus can do, includes vision, has solid browser automation — and you own it.
• 4:36
  Kimi's pricing through Cloudflare makes this even more stark: $0.14 per million input tokens if you're on B200s with their optimizations.
• 4:47
  Anthropic charges $15 per million for Opus.
• 4:50
  That's a regime change.
• 4:52
  The feedback from early adopters reads like a capability checklist.
• 4:57
  Augment Code's evaluation: "K2.6 is noticeably more effective than K2.5 at navigating nuanced API behaviors and recovering when things break." OpenCode: "Kimi K2.6 proves to be exceptionally reliable...
• 5:13
  a sharper grasp of task requirements and more streamlined multi-step operations."
• 5:24
  OpenCode asked their users today if they should triple the K2.6 limits.
• 5:30
  The vote wasn't close.
• 5:32
  Every closed-source advantage in coding is now temporary.
• 5:36
  When an open model matches your flagship product at one percent of the price, your moat isn't technical capability anymore.
• 5:46
  It's ecosystem lock-in, memory systems, and enterprise contracts.
• 5:51
  Which brings us to OpenAI's answer to that exact problem.
• 5:55
  OpenAI dropped Chronicle today — their expansion of Codex's memory system.
• 6:01
  The pitch is elegant: Codex now understands context from what's on your screen.
• 6:06
  Your actual screen.
• 6:07
  From their announcement: "With Chronicle, Codex can better understand what you mean by 'this' or 'that.' Like an error on screen, a doc you have open, or that 'thing' you were working on two weeks ago."
• 6:24
  Chronicle runs background agents that continuously capture your screen, building memories from what you're working on.
• 6:33
  Those memories are stored locally on your device — for now — and Codex can reference them to maintain context across sessions.
• 6:42
  No more re-explaining your project structure.
• 6:45
  No more pasting the same error messages.
• 6:48
  No more "as we discussed yesterday" preambles that waste tokens and time.
• 6:53
  Harrison Chase from LangChain saw it immediately: "memory will be the great lock in.
• 6:59
  and everyone knows it, so are rushing to get there first."
• 7:04
  Once Codex knows your codebase, your patterns, your specific environment quirks — switching to another tool means starting from zero.
• 7:13
  OpenAI isn't selling you a model anymore.
• 7:16
  They're selling you continuity.
• 7:19
  But here's what's fascinating about the rollout: Pro users only, macOS only, and explicitly excluding EU, UK, and Switzerland.
• 7:28
  That geographic carve-out isn't about technical limitations.
• 7:32
  It's about privacy regulations.
• 7:34
  Because Chronicle doesn't just see your code — it sees everything on your screen.
• 7:40
  Banking tabs.
• 7:41
  Email.
• 7:42
  Slack messages.
• 7:43
  Everything.
• 7:43
  Jake Bloom raised the obvious concern: "If Codex has a prompt injection vulnerability, an agent with continuous screen access has a larger blast radius than a stateless assistant."
• 7:59
  A disclaimer that "other apps may access these files" stored on your device.
• 8:04
  That's a security model built on crossed fingers.
• 8:07
  The tension here is real.
• 8:09
  The feature is genuinely useful — multiple developers confirmed it eliminates the constant context restatement that kills flow.
• 8:18
  But you're trading that convenience for a system that watches everything you do, stores it locally in a way other apps can access, and creates lock-in through accumulated context.
• 8:31
  And the token consumption is extraordinary.
• 8:34
  Chronicle burns through rate limits building these memories.
• 8:38
  OpenAI is literally charging you to create the context that locks you into their platform.
• 8:45
  Sam Altman didn't announce this as a memory system.
• 8:48
  He called it telepathy.
• 8:50
  When your CEO is using that kind of language for what amounts to screen recording plus RAG, you know the lock-in is the point.
• 8:59
  Tim Cook is stepping up to Executive Chairman on September 1st.
• 9:03
  John Ternus, who's been running hardware engineering, takes the CEO role.
• 9:08
  The timing is exquisite.
• 9:10
  The numbers tell Cook's story: Apple went from $350 billion to $4 trillion in market cap.
• 9:16
  Revenue quadrupled.
• 9:17
  The iPhone scaled from one model in two colors to five models in dozens of colors selling hundreds of millions of units.
• 9:25
  Operational excellence personified.
• 9:28
  But Cook is leaving right as the game changes completely.
• 9:32
  As Ben Thompson noted in Stratechery today, Cook's great triumph was scaling Jobs' last breakthrough — the iPhone — to planetary scale.
• 9:41
  Cook didn't create new categories; he perfected existing ones.
• 9:46
  Even the Apple Vision Pro, Cook's one attempt at a zero-to-one product, is — as Thompson puts it — "more of a 0.5."
• 9:56
  Every major tech company is racing to build agent platforms.
• 10:00
  Microsoft has Copilot embedded across Office.
• 10:03
  Google's launching Rosalind for life sciences research through Codex.
• 10:08
  OpenAI's Chronicle is creating ambient computing context.
• 10:12
  And Apple?
• 10:12
  Apple's shipping incremental hardware updates and taking 30 percent of App Store revenue.
• 10:19
  Sam Altman's tweet was gracious: "Tim Cook is a legend.
• 10:22
  I am very thankful for everything he has done and I am very thankful for Apple." But there's subtext.
• 10:29
  Altman runs the company that's building the infrastructure for the agent economy.
• 10:35
  Cook ran the company that perfected the smartphone economy.
• 10:39
  These are different games requiring different leaders.
• 10:43
  John Ternus is a hardware engineer.
• 10:45
  He's overseen the Apple Silicon transition, which was brilliant.
• 10:50
  But the question isn't whether Apple can build better chips.
• 10:54
  It's whether Apple can build an agent platform that developers want to use when Kimi K2.6 runs locally, Claude Code modifies itself, and OpenAI's Chronicle creates sticky context.
• 11:06
  The quiet part that Thompson says out loud: Cook prioritized Apple's financial results and shareholder returns over developer ecosystem health.
• 11:16
  That worked when Apple controlled the only game in town.
• 11:20
  But agents don't care about your App Store policies.
• 11:24
  They don't need your approval.
• 11:26
  They run where they run.
• 11:27
  Cook's timing is actually perfect — for Cook.
• 11:31
  He's leaving at peak valuation, before the bills come due on a decade of developer antagonism, right as the game shifts to something Apple isn't positioned to win.
• 11:42
  The question isn't whether Ternus is a good CEO.
• 11:45
  It's whether anyone can redirect a $4 trillion battleship that's been optimized for extracting rents from mobile apps while the entire industry shifts to autonomous agents that don't need permission to exist.
• 12:00
  Wanye asked the question everyone's thinking but few want to examine: "I don't have to be convinced that LLM's make programmers more productive.
• 12:10
  But where's all the stuff?
• 12:12
  We've now had months and months of 100x or 1000x programmer productivity improvements.
• 12:19
  Where's all the stuff they're building?"
• 12:24
  Simon Sarris points to his projects — floracarta.com, meetinghouse.cc.
• 12:29
  Individual creators building individual tools.
• 12:32
  But that's not 100x more stuff.
• 12:35
  That's the same amount of stuff built faster.
• 12:38
  Sierra_tech_ had the honest answer: "most of it is internal tooling, automation, and features inside existing products.
• 12:47
  the 100x productivity gain doesn't always produce a 100x visible output, a lot of it just made the same amount of stuff with fewer people."
• 12:58
  The productivity gains are real.
• 13:01
  But they're not creating an explosion of new products.
• 13:05
  They're allowing companies to maintain the same output with dramatically smaller teams.
• 13:11
  This explains something crucial about the current moment.
• 13:16
  Anthropic just announced plans to spend $100 billion on AWS compute over the next decade — the largest cloud commitment in history.
• 13:25
  OpenAI's funding rounds now measure in the hundreds of billions.
• 13:30
  The infrastructure investment is astronomical.
• 13:34
  But the output isn't new consumer products.
• 13:37
  It's efficiency.
• 13:38
  It's cost reduction.
• 13:40
  It's doing the same with less.
• 13:42
  Yohei Nakajima captured a different angle: "happy monday!
• 13:46
  hope you have a week full of wins and smiles :) (also, rotate your secrets)."
• 13:54
  It's the constant background anxiety of the agent age.
• 13:58
  Everything is accelerating, including the attack surface.
• 14:03
  The same tools that let one developer do the work of ten also let one vulnerability impact thousands of systems.
• 14:11
  The productivity paradox reveals something uncomfortable: AI isn't expanding the pie yet.
• 14:18
  It's making the existing pie cheaper to produce.
• 14:21
  That's valuable — efficiency always is — but it's not the revolution we were promised.
• 14:28
  Or maybe it is, just not the way we expected.
• 14:31
  Revolution doesn't always mean more.
• 14:34
  Sometimes it means the same with dramatically less.
• 14:37
  And dramatically less need for humans is a revolution of a different kind.
• 14:43
  Jeremy Howard surfaced something that should terrify everyone building on this infrastructure: "Anyone know whether OpenAI officially supports the use of the /backend-api/codex/responses endpoint that Pi and Opencode (IIUC) uses?
• 15:00
  It doesn't seem to be documented, and was reverse engineered by Simon Willison."
• 15:08
  Some of the most popular coding agents in production — tools writing actual production code at actual companies — are built on an endpoint that OpenAI has never documented.
• 15:21
  Simon Willison had to reverse-engineer it.
• 15:24
  And now thousands of developers depend on it.
• 15:28
  Max Slinger's response was perfect: "wait so multiple popular tools are running on an endpoint simonw had to reverse engineer?
• 15:37
  that's gonna be a real fun morning when OpenAI changes it."
• 15:48
  So far OpenAI seem ok with it...
• 15:51
  Official?
• 15:52
  Unclear.
• 15:52
  Perhaps 'tolerated'."
• 15:55
  That word captures this entire ecosystem.
• 15:58
  Anthropic tolerates CLI usage until they don't.
• 16:02
  OpenAI tolerates undocumented endpoint usage until they don't.
• 16:06
  Apple tolerates developers until the rent comes due.
• 16:10
  We're building the future of software development on infrastructure that exists at the pleasure of companies that can't maintain consistent policies week to week.
• 16:22
  Claude Code is modifying itself using interfaces that might not exist tomorrow.
• 16:28
  Thousands of developers are shipping code through Pi and OpenCode using endpoints that were never supposed to be public.
• 16:37
  And the alternative?
• 16:39
  Kimi K2.6.
• 16:40
  Open source.
• 16:40
  Run it yourself.
• 16:42
  No policies to change.
• 16:43
  No endpoints to deprecate.
• 16:45
  No memory systems creating lock-in.
• 16:48
  The pattern is clear.
• 16:50
  Every attempt to create sustainable agent infrastructure through closed providers hits the same wall: the provider's interests diverge from the developer's needs.
• 17:02
  OpenAI wants lock-in through memory.
• 17:04
  Anthropic can't decide if they want third-party usage at all.
• 17:09
  Apple wants their 30 percent cut of everything.
• 17:13
  Meanwhile, the open models keep getting better.
• 17:16
  K2.6 matches Opus.
• 17:17
  The next version will match whatever comes after.
• 17:21
  The version after that will exceed it.
• 17:24
  Paul Graham captured something essential in his 4:30 AM essay writing session: "Wake up at 4:30 am.
• 17:31
  Essay starts forming in my head.
• 17:34
  Since I'm staying in a hotel, my laptop is right there, so I get up to at least write down the sentences I already have.
• 17:43
  Two hours later I've written the whole thing."
• 17:49
  The idea arrives, the tools are there, the work happens.
• 17:53
  No permissions needed.
• 17:55
  No policies to check.
• 17:57
  No undocumented endpoints to worry about.
• 18:00
  The irony is perfect.
• 18:01
  At the exact moment AI agents gain the ability to modify their own code, the infrastructure they run on has never been more fragile, more policy-dependent, more hostile to the developers building on it.
• 18:16
  The solution isn't better documentation or clearer policies.
• 18:21
  It's infrastructure you actually control.
• 18:24
  Models you can modify.
• 18:26
  Endpoints that can't disappear.
• 18:28
  Code that belongs to you.
• 18:30
  The harness is modifying itself.
• 18:32
  The question is whether it's modifying itself on infrastructure that will exist tomorrow.
• 18:39
  That's what I'll be watching.
• 18:41
  Lenar Kess.