An Exploded View publication

Reading Room

Vol. 1 · No. 62 Thursday, October 29, 2026 aikansh.com

This week's theme

What your systems do when nobody is checking

Today's stories show systems doing things nobody checked: a coding tool calling home every 30 seconds, a shared AI model leaking customer data, and a sovereign cloud that still runs through Google.

A 15-minute read · 13 stories

In this issue

01 Front Page

Claude Code sends full agent transcripts to itself every 30 seconds

Each check-in was meant to write a one-line status update, but it was burning as much as a fifth of all requests before anyone noticed.

Claude Code, Anthropic's coding tool, has been quietly checking in on itself. This matters because you run background agents constantly, so it touches your own costs and privacy. Every roughly 30 seconds, for each agent working in the background, Claude Code sends that agent's entire conversation back to its own model. That model is usually Opus, Anthropic's most capable and most expensive one. It asks the model to describe its last action in 3 to 5 words. The answer only updates one line of text in the agent status panel. It never reaches your conversation or the model actually doing the work.

A developer named DRIM caught it. He read Claude Code's OpenTelemetry export, a detailed log of every request it makes and why. Before anyone noticed, these check-in requests made up 16.4 percent of Claude Code's own estimated spend. The main conversation itself was only 15.7 percent. The check-ins also made up 19.7 percent of all requests, about one in five. Ninety-six percent of that spend ran on Opus. Each request sent roughly 9,000 tokens (chunks of text, about three quarters of a word each) in, just to get one token of answer back out. A separate GitHub thread, issue 86879, collected four independent measurements putting the waste at 18 to 26 percent. This was not a one-off bug report. The feature has run by default since version 2.1.232, released in August 2026, and there is no setting to turn it off. On a pay-per-use plan this shows up as real dollars. On a flat subscription like yours, what you lose instead is rate-limit headroom, the room you have before you hit your usage cap.

The fix is a free script called no-agent-summary.js, about 80 lines long, written by a developer going by Flamerix AI under the MIT license. It is a preload script: a small file loaded into the program before it starts. It is built for Bun, the JavaScript runtime Claude Code runs on. The script wraps the timer functions the status check uses. When a timer's code contains a specific marker left over from the summary feature, the script swaps in a dummy timer that never fires. Every other timer keeps working normally. The trick works even though Claude Code ships its code pre-compiled, because a quirk of JavaScript still lets the script read a timer's original source text to check for that marker. After installing it, the same share of requests dropped from 16 to 19 percent down to zero within two days.

Installing it takes three steps. Download the script, set an environment variable called BUN_OPTIONS to preload it, and restart Claude Code's background daemon, the helper process that keeps your sessions and background agents running. Scripted or scheduled runs need the same fix, not just the interactive app. The author tested it only on Linux, on Claude Code versions 2.1.257 to 2.1.312, and says macOS and Windows are untested. On your Mac mini and MacBook, that means checking it works before you trust it. The fix is also fragile by design: it matches one specific string inside Claude Code's code. A future update that renames that string would silently bring the check-ins back with no warning.

The post hit Hacker News's front page with 415 points and 153 comments, a sign plenty of other people ran into the same cost surprise. The script includes its own way to verify it is working: point it at a log file, run a background agent for a minute, and the log should show the summary timer being suppressed while the agent's status panel stops updating.

Every ~30 seconds, for every background agent, Claude Code sends that agent's entire transcript to the agent's own model (usually Opus) and asks it to "describe your most recent action in 3-5 words".
via Gist →
02 Key News

A single text message can disable an Android phone's calls

Outside your usual reading: this is a mobile security write-up, not an AI story, but the lesson travels.

A single text message can crash an Android phone's call app and drop any call in progress, including a call to emergency services, with no action needed from the phone's owner. Independent researchers reproduced the attack with a 100 percent success rate on a Pixel 9 running April 2026 software and on several Samsung Galaxy and A-series phones.

The message is a type called a WAP Push, a short format phones use to receive links and settings pushed from a carrier. Android's phone app reads a length value out of that message and is supposed to check that the value makes sense before using it. It does not. The flaw sits in a function called decodeWapPdu, inside a file named WapPushOverSms.java, where the code reads the length as a large number type, converts it down to a smaller number type with no range check, then uses that converted number as the size of a new block of memory to allocate. A crafted value decodes to a number that, once converted down, becomes negative 2,147,483,648. Asking the phone to allocate a block of memory of a negative size throws an error the phone app never catches, and the app crashes and restarts. The message never appears in the phone's inbox, and the owner never sees who sent it or that anything happened.

A single message produces one crash and one restart, a short, repeating outage each time it lands. Sending about 30 of the messages in quick succession is worse: the repeated crashes collide with the phone app's own writes to its message database at the same moment, and that collision corrupts the database file. Once that file is damaged, the phone app no longer needs a new malicious message to fail. It crashes every time the phone starts up, simply trying to read its own damaged records.

The researchers argue this is not a minor bug because of where it lands: a phone that cannot reliably place a call cannot reliably reach emergency services either. Losing emergency call access is treated as a public safety failure on its own, and this bug can manufacture that exact failure remotely, with a text message the victim never sees. The rule was tightened in 2024 after some phones were left able to make ordinary calls but not emergency ones during an older network shutdown, the same end result this bug produces by a different route.

The fix is small: add a check that rejects the length value before it gets converted and used, instead of trusting it. The researchers handed Google that exact fix the day they filed their first report. Google's own bug bounty program reviewed the report three separate times, including two appeals, and each time classified it as not a security issue. The program has its own category for exactly this shape of bug, a destructive remote denial of service, meaning it disables a device in a way that needs more than turning it off and on again to fix. The researchers published the full writeup and a working proof-of-concept only after the standard disclosure window had passed with nothing shipped.

The detail to keep past the specific Android bug is the shape of the failure: a boring, easily reviewed mistake, a number not range-checked before a type conversion, turned into a remote, no-interaction denial of service that can repeatedly disable a phone's calls, including emergency calls. That exact category of mistake is what code review and tests are supposed to catch before anything ships, in his own agents' output as much as in a phone's operating system.

via SMS of Death →

Four takeaways from Anthropic's record stock filing

A news roundup pulls four takeaways from Anthropic's filing for what could be a record breaking stock market listing, though the specifics aren't given in this save. Anthropic is the company behind Claude, the tool his whole operation runs on, so the terms of its listing are worth tracking as more detail surfaces.

via The Guardian →

Anthropic's CEO pushes for stronger AI regulation

Anthropic's chief executive is publicly calling for stronger government regulation of AI, according to an ABC News exclusive. Regulation sets the rules every AI company, including Anthropic, has to ship under, which shapes the tools his whole operation depends on.

via ABC News →

OpenAI and ServiceNow deepen their enterprise partnership

OpenAI and ServiceNow are deepening their partnership: OpenAI's models and agents, meaning AI that takes several steps on its own, are going into ServiceNow's workflows, and ServiceNow's workflows are going into ChatGPT and Codex. It shows how fast AI vendors are wiring themselves into everyday business software, worth watching if he ever sells into companies running these tools.

via OpenAI →

Musk's AI remake of the Odyssey draws heavy criticism

Elon Musk made a short AI-generated film based on The Odyssey, the ancient Greek story, and said he wanted to beat a version made by director Christopher Nolan. Viewers who watched it called it low quality and far from the original story, a real data point on where AI video still falls short of a human-made production.

via reddit r/ArtificialInteligence →

Oura pulled its IPO, a line-by-line filing read shows why

Oura pulled its public stock offering, but an investor who read the filing line by line found a different explanation: of 50 million shares on offer, 36.5 million were existing shareholders cashing out, leaving Oura only about $567 million against roughly $1.5 billion going to sellers, with about 93 percent of that already earmarked for employee tax bills.

via reddit r/ArtificialInteligence →

A valuation professor publishes his own Anthropic estimate

Valuation professor Aswath Damodaran has published his own independent estimate of what Anthropic is worth, separate from whatever number its stock market listing lands on. A credible outside check on whether Anthropic's eventual public price reflects the real business or just IPO excitement.

via Aswath Damodaran | Substack →

Anthropic launches tools to track AI spending value

Anthropic has launched new tools that show companies exactly what their AI spending is buying them. Spending visibility is the first thing any company, including his own ventures, needs before it can judge whether AI tools are worth the cost.

via TechCrunch →

Starling Bank's sovereign AI still runs on Google and NVIDIA

Starling Bank, a British challenger bank, says it is building what it calls the first banking AI model trained entirely on UK sovereign cloud, meaning cloud computing kept physically and legally inside one country rather than run by a foreign company. A newsletter that read past the announcement found the claim only holds with three qualifiers it did not spell out in full, plus a more basic problem: when Starling made the announcement, the model had not actually been trained on real customer data yet.

The model is due to start running Starling's fraud detection from early 2027, and later power an AI assistant for the bank. That timing matters because at least three other lenders are already running similar transaction-monitoring AI models today, and one of them is already doing it on a non-US cloud, which cuts against how novel Starling's first claim really is.

The sovereignty claim has a hole in it. Starling's sovereign setup routes customer data through Google Cloud before that data ever reaches Civo, the UK-owned cloud provider that is supposed to be the sovereign part of the story. So the data still passes through a large American cloud company on its way to the British one, even as the bank markets the setup as independent of big technology infrastructure.

The newsletter's fuller comparison, including who built similar banking models first and with how much more training data, sits behind its paywall, so that detail is not available here. What is confirmed is the pattern worth watching: a sovereign AI label applied to a system that, underneath, still depends on the same handful of large cloud and chip companies everyone else depends on. For anyone evaluating a vendor's claim of independence from big technology, the Starling case is a reminder to ask what actually touches the data before it reaches the sovereign part of the pipeline, not just what the marketing says.

via Linas's Newsletter →
03 Insights

Stripe launches free instant payments for AI agents

Stripe Pay lets AI agents pay businesses directly, for free, instantly.

Stripe, the payments company behind the "pay" button on a lot of websites, launched a free, instant way for businesses to pay each other on October 27, called Stripe Pay. This lands on his desk because he is building his own fleets of AI agents (software that takes several steps on its own, without a person approving each one), and payments is becoming the next layer of plumbing that big companies are racing to own for those agents.

The core idea is a "handle": a verified business address that lets an AI agent pay another business without guessing a bank routing number. Businesses on Stripe already pay each other 4.8 million times a day. With Stripe Pay, a business, or an AI agent working for it, can look up another business by name and settle the payment for free and instantly on Stripe's own ledger (its internal record of who paid whom), instead of routing through an outside bank. It shipped as a simple command-line tool (a typed text command, no screen needed) and a button in Stripe's dashboard.

The free transfers may not be the real prize. When both sides of a payment are Stripe businesses, Stripe gets to choose which rail (the route the money actually travels) the payment uses, rather than a bank or card network choosing. That makes Stripe's directory of verified business handles look like the valuable asset: whoever owns the directory AI agents trust becomes the default way agents pay each other. The newsletter flags three follow-on arguments it plans to make, that banks lose before Visa does, that Stripe's handles collide with Visa's own plan for identifying agents, and that the launch connects to Stripe's push into lending, but the piece is paywalled past the launch details, so those specific arguments aren't available here.

Businesses on Stripe already pay each other 4.8 million times a day.
via Linas's Newsletter →

Why AI might create new wants, not just replace jobs

A Reddit essay compares AI's hype to electricity and computers' early days.

A Reddit post lays out a simple historical pattern worth borrowing when guessing where AI actually goes next: every powerful new technology first gets sold as doing existing work faster, and only later does it create entirely new things people want that did not exist before. For someone building AI agent fleets, this is a useful check on assuming AI's main effect will be replacing workers.

The post's first example is electricity. When the electric grid first spread, it was sold as a labor replacement, something that could do the work of many people. Today the average US household uses about 10,500 kilowatt-hours of electricity a year, but almost none of it powers labor. It runs televisions, music, refrigerators, air conditioners, heaters, and lights: desires that did not exist before electricity existed to satisfy them.

The second example is computers, literally named for the labor they replaced: "computing power" meant doing the work of many human calculators at once. The post's thought experiment: take a smartphone back to 1969 and tell a NASA scientist it holds a million times more computing power than the machines that landed astronauts on the moon. He would likely ask whether everyone is now launching rockets from home. The real answer turned out to be TikTok, dating apps, streaming video, and online gaming, none of which existed as a desire before the computing power did.

The post's point is that AI is getting the identical pitch right now, that it can do the work of hundreds of coders and will replace workers, and that framing misses the pattern every time it has played out before. Its challenge to the reader: if you met someone from the future and asked whether AI replaced nearly every human worker, the honest answer is probably no, not because AI undershoots, but because by then it will have created new desires nobody today can picture, the same way nobody in 1969 could picture TikTok. The author, who notes English is not their first language and used AI only to check grammar, ends by asking what those new desires might be, without answering it themselves.

Desires that didn't exist before electricity created them.
via r/ArtificialInteligence →
04 Learnings

What a buy-side broker actually does and costs

A buy-side broker works only for the buyer in a business purchase, running the search and deal process to your criteria instead of maximizing the seller's price. Fees run $2,500 to $7,500 a month plus a cut at closing, or $150 to $350 an hour, worth comparing against sites like Axial and the IBBA directory for your own SMB search.

via Axial →
The Last Word
The bug is rarely clever. Usually it is a setting nobody read.
The Desk Report

How this edition came together — from bookmarks and feeds to the page.

217links gathered
40read by the desk
14made the edition

Where they came from

On the cutting-room floor — 26 links read but not run this week

Quality over volume: most links get a second look and a pass. The ones that made it earned their place.

Reading Room — every Sunday

The week's AI signal in 15 minutes — what happened, why it matters, and what to do with it. Curated by someone who actually builds, not a feed algorithm.