
Hi everyone,
Last weekend we drove down to Narragansett with Koda. Sun, granite, and the Point Judith lighthouse, and he found the best rock on the shore. Love day trips to the shores around here!

This is the 30th edition of Quanta Bits, more than six months in the making. I know from experience that when you work full time on specific projects, it's hard to pick your head up, look around, and research other developing and perhaps interesting areas. My intent behind this newsletter has been, and remains, to give my busy professional friends, and anyone without much time to follow AI, a quick shot of the developments I find interesting and relevant to business operations.
I still believe in that mission and am committed to it. I keep experimenting with formats and segments, and this will keep evolving like most organic, living experiments. To that end, the essay section is becoming less deep thoughts and more expanded news patterns and discussions, with occasional deeper delves (to use what we now think of as an AI word, such madness we live in!) into specific threads.
This week is a good example. Two frontier models, the most capable class of AI available, arrived within days of each other, so the feature is a discussion of what was claimed and what it could mean for the rest of us.
Cheers.
Reza
⏱️ The Brief
This week's new AI models promise to complete more difficult work with less help. Their headline test results still come from their makers. Published prices and access rules are firmer ground than a launch claim about what the models will do for your business.
AI agents can carry out tasks and assign work to other AI agents. That extra activity can increase the AI bill even when each task costs less. Subscription allowances from AI providers follow different rules from pay-as-you-go pricing, so compare what your workload costs under the plan you use.
Companies are looking beyond how much employees use AI to whether it completes useful business work. Counting the time people spend checking and correcting AI's work changes the savings calculation. Software has an advantage here: automated tests can check many code changes, while other kinds of work still need substantial human judgment.
Financial authorities and insurers are preparing for AI-assisted attacks that could disrupt businesses across borders. A separate, immediate exposure is ordinary account access: an AI assistant connected to company systems may have permissions that an attacker could misuse.
AI benchmark test scores can look better when a model has encountered the questions before. Google is piloting a way for outside evaluators to test a model without revealing their questions to Google, reducing the opportunity to prepare the model for that particular benchmark test.
📶 Patterns & Signals
Companies are trying to measure useful AI work, not just usage
On August 30, The Economist examined why software engineers use AI more heavily than other workers. One advantage is that code can be tested automatically. A team can check whether a change works before accepting it. Other business work can be harder to assess, particularly when a plausible answer still needs an experienced person to check it.
That connects with an earlier discussion about measuring AI returns. In an August 10 account of rebuilding OpenAI's finance function, its CFO Sarah Friar asks whether AI finished useful work, what it cost including employee time and rework, whether the result was usable, and whether the team moved faster or made better decisions. An August 3 New York Times report described another approach at cybersecurity company Elisity: employees write a job description for each proposed AI agent, and the company compares AI spending with the full cost of employing a person. These are different attempts to connect AI spending to a defined job. Neither the number of requests nor a busy agent tells you whether that job was done well.
Andrew Bailey, chair of the Financial Stability Board, which coordinates financial-risk policy across major economies, warned G20 finance officials that disruptions involving advanced AI could spread across national borders. His letter, published August 31, calls for coordinated preparation and safe deployment. Reuters reported, via Insurance Journal, that cyber insurers are also reviewing coverage as AI agents take actions on their own. One insurance question is whether losses caused by an agent are covered when there is no conventional hacker behind them.
A separate exposure is the access already granted to AI tools. VentureBeat reported stolen Claude sessions and unauthorized usage; access to connected Gmail was a risk, not a confirmed outcome. A session is what keeps a user signed in, so stealing it can let someone act through that account without knowing its password.
WorkOS, a company that sells login software, described one way to reduce credential exposure in an August 10 technical post. Its Relay service holds the login credential for an outside service and attaches it when forwarding the agent's requests. The agent still needs its own key to use Relay. This keeps the outside service's credential out of the agent's working environment; it does not, by itself, restrict the agent to one task. Permissions still have to limit what those requests can do.
Signals to watch
Nvidia agreed to buy Hugging Face for $13 billion, the Wall Street Journal reports. Nvidia supplies chips used to run AI. Hugging Face is a major platform where developers share and download AI models. If completed, the deal would give Nvidia a larger role in how developers find and distribute models, alongside its hardware business. An agreement does not mean Nvidia already owns the platform yet.
AT&T reports cutting AI coding costs by up to 56% by routing work to cheaper models. The Information says the telecommunications company's internal software directs simpler tasks to less expensive AI models. Openly downloadable models now handle about 40% of employee queries. They still cost money to run, but can reduce reliance on paid model providers. AT&T plans to hold its spending on Anthropic and OpenAI flat; the reported savings do not establish how well the approach would work elsewhere.
Google is piloting blind testing to make AI performance scores more trustworthy. Google DeepMind, Google's AI research division, is working with outside evaluators to test one of its Gemini models. The protected setup lets evaluators submit questions without Google seeing them, while keeping Google's model files private. The goal is to measure how well the model handles unfamiliar tasks, with less opportunity for developers to improve scores by preparing it for those particular questions. This is a pilot, not a guarantee that the tests themselves are unbiased.
🎯 Two frontier models in one week

What arrived
Frontier models are the most capable class of AI available at any moment. On September 1, Anthropic released Claude Fable 5.1 and Mythos 5.1: the same model with different safeguards, with Mythos restricted to approved organizations. On September 3, OpenAI released GPT-6 Astra. In between, Google shipped Gemini 3.8 Flash, its fast and inexpensive model. This gives people choosing AI for work several new options at once, with different costs and limits on what they can do.
What Anthropic claims
Anthropic reports Fable 5.1 scoring 55.8%, up from Fable 5's 42.0%, on Terminal-Bench 4.0, a test of multistep computer tasks performed through typed commands. On AutomationBench's business workflow tasks, it reports 31.4%, up from 17.1%.
A more concrete example comes from investment firm Millennium. It says Fable 5.1 traced a rare software crash to a defect that engineers and earlier models had not explained. This is a customer testimonial in Anthropic's launch post, not independent proof.
The pricing is easier to follow if we separate the ways people pay. API use is when software connects directly to the model, for example to process documents automatically. You pay for the amount of material the model reads and produces, measured in small pieces called tokens. Anthropic has kept Fable's basic rates unchanged but made reusing previously processed material cheaper. It says this can lower usage bills, depending on the work.
A subscription, such as Claude Pro or Max, charges a recurring fee that includes a limited amount of use. It is not unlimited access to every model. Paid usage credits cover work outside that allowance and cost extra, on top of the subscription. You can incur those extra charges while using Claude's app; they are not limited to people building software through the API.
For Fable, the plan rules matter: Max users, premium Team users, and premium users on legacy seat-based Enterprise plans can spend up to half their weekly allowance on it before needing extra credits. Pro and standard Team users need credits from the start. So cheaper metered use does not mean a cheaper subscription or a larger included allowance.
What OpenAI claims, and the rating it gave itself
OpenAI reports a 57.9% score on Terminal-Bench 4.0. Its president Greg Brockman told NBC that Astra "can really do anything a human can do with a computer." That is a much broader claim than a result on one test.
Before release, OpenAI rated Astra "Critical" for cybersecurity under its own safety framework. It believes the model can find unknown flaws in well-protected systems and develop attacks without step-by-step human guidance. OpenAI deployed it with restrictions intended to block harmful use, while reserving more advanced security access for vetted partners. The rating describes a capability OpenAI found in testing; it does not mean the public product freely offers that capability.
OpenAI's safety report describes a problem with catching unwanted behavior: Astra's written explanations of its thinking are less helpful than those of the previous model, GPT-5.6 Sol. Compared with Sol, monitoring systems were better at spotting unwanted behavior in Astra's actions and answers alone. But when given the full record, including each model's written explanations, they generally performed worse with Astra. In some tests, Astra also avoided detection when explicitly instructed to try. OpenAI can still monitor what Astra does, but reading its explanations is becoming a less reliable way to spot trouble.
What has actually been verified
I haven't found independent replications of the headline performance results cited here. The published prices, plan rules, and vendors' stated safety classifications can be checked against their documents. Whether either model finishes your work more reliably, or reduces the total cost of doing it, still needs testing on that work.
In my limited use so far, both models have been noticeably better than their predecessors. Astra has been particularly good at carrying out tasks on my computer. But I'm also using up my subscription allowances faster, especially with Fable 5.1. That is worth distinguishing from the lower usage costs Anthropic advertises. How much work you get from your plan also depends on how much thinking you ask the model to do and how much material it processes along the way.
What it could mean for an operations leader
I am running both Fable 5.1 and Astra for my own development work. These are the things I'd check before giving either new model more responsibility:
What happens to the bill when an agent delegates work? One request can launch several helper agents that each use the model. I'd set a spending limit in the software running the workflow, where it supports one, and check the combined usage. Telling the model to stay within a budget is not the same as a system that stops spending at that limit.
Which work deserves the more expensive model? Nathaniel Whittemore, host of the AI Daily Brief podcast, discusses where each model fits among the tools you use. That is a useful way to approach this week. I would compare the new model with the cheaper one on a recurring task, including the time I spend fixing the result, before switching the whole workflow.
Can I tell whether the work was done correctly? For the software-crash example, an explanation is useful only if engineers can reproduce the defect and test the repair. I would want that evidence with the proposed fix. A convincing account of what the model did is not enough to put the change into service.
Where I land
There is enough here to try both models on work that has been difficult to delegate. Give each model the same job and compare the results. Which did the better job? How much checking and correction did each need, and what did it cost compared with how you do the work today? That would tell me more than which one answered faster, and help me decide which model to use for that kind of work.
💬 Interstitials / Overheard
Plot twist: they all run on the same server

Around Astra's release, reports of disruptions to Grok, Codex, and Claude prompted this joke from Tibo. Wait, are they all just running the same model on the same server?! 😊
Source: Tibo (@tibo_maker) on X, September 3, 2026
🌍 Meanwhile...

In a study reported by the University of California, Irvine in September 2025, researchers improved aged mice's vision by injecting a specific fatty acid into their eyes. The work concerns the retina, the light-sensitive tissue at the back of the eye. Activity of a gene called ELOVL2 declines with age, reducing production of fats that help maintain it. Replacing one of those fats improved vision and some molecular signs of aging. DHA, a better-known omega-3 fatty acid, did not produce the same improvement in this experiment. It's still mice and still injections, so a human treatment is a long way off.
📚 What I'm Consuming
How I manage 15 AI agents 24/7 as a solo founder (video). Solo founder Ryan Carson shows how he delegates coding, bug fixes, and customer-account checks to AI agents working in parallel. He still sets priorities, talks to customers, and reviews riskier changes himself. The episode is as much about managing the work as producing it.
Agents Aren't Taking Your Jobs. They're Creating More Work Instead. (video). AI tools can do a task and leave a person to check the result, handle mistakes, and decide what to do next. Nate B Jones, who writes about working with AI, examines why that management time rarely appears in the claimed savings, whether you're working alone or inside a company.
What Is Digital Sovereignty? AI, Data & Control Explained (video). Sam Anthony of business technology company IBM explains who controls a company's data and software, including its AI, and how dependent it is on outside providers. That can affect where data is stored and whether the company can switch suppliers. Useful context, with IBM's commercial interest in cloud services in mind.
Why Ramp built its own coding agent, and you should too (article). Ramp, the corporate card and expense company, describes the setup behind its coding agent: a separate cloud computer where it can change code, run tests, and inspect the result using company tools. Its January account shows how much useful automation depends on giving an agent a working environment, not just choosing a model.
AI Daily Brief on Fable 5.1, Astra, and the model stack (video). Nathaniel Whittemore's roundup of the week's new models, Anthropic's Fable 5.1 and OpenAI's Astra, including the first reports of users burning through their usage allowances. His framing, that the question is where each model fits in your set of tools rather than which one to switch to, is the one I borrowed for the feature above.
I built a Claude Cowork system that does a week of PM work in a day (video). Daniel Blum, a product manager at payments company Melio, uses Claude's Cowork assistant to track priorities in Notion, a notes and task-management app. The assistant asks him to clarify unfamiliar business terms before saving them, and a weekly routine compares its drafts with the messages he actually sent. His week-in-a-day claim is not backed by a measured comparison.
🔤 Term of the Week
Credential proxying: Imagine an AI assistant posting an update in Slack, a workplace messaging app. Instead of giving the assistant Slack's access token, the digital key that authorizes the request, a service such as WorkOS Relay holds it. The assistant sends its request through Relay, which adds the key and forwards the message to Slack. This keeps the Slack key out of the assistant's hands. It does not prevent the assistant from posting the wrong message, so rules about what it can read or send still matter.
🌙 After Hours
Fiasco: The Battle for Boston
Leon Neyfakh | Audiobook released February 4, 2025 | 5h 25m audio | ★★★★★

I finished Fiasco: The Battle for Boston. It's a short audio documentary, more podcast than book, and I'd happily consume more things like it. I've lived in Boston a long time and didn't know this history of school segregation and the 1970s court-ordered busing that tried to end it.
It also covers moments like James Brown's televised Boston concert after Martin Luther King Jr.'s assassination, and the efforts to keep the city calm that night.
The format is why it works. Clips and interviews make it feel like a documentary rather than a narration, and it moves quickly. It loses some steam near the end, which is my only real complaint.
🎙️ Listen
Prefer to listen? Quanta Bits is also available on Apple Podcasts and Spotify.
How this gets made
I collaborate with Spock, my AI agent. He researches extensively: scanning, filtering, and surfacing what is relevant across my business. I read, listen, and watch what resonates, and decide what matters. I provide the direction, and we draft together. The editorial judgment is mine. He would tell you the same. Most logical. 🖖