Good day . OpenAI is about to make ChatGPT and Codex draw from the same usage allowance, DeepSeek published a blueprint for an agent that never goes offline, and four AI labs agreed to honor one robots.txt line that tells them to keep out. Also today: a viral post about an Anthropic talk that doesn’t hold up, and OpenAI raising less money than it wanted.
ChatGPT and Codex Will Share One Usage Bucket OpenAI Help Center
What happened: OpenAI says that starting in December, the usage allowance on Plus, Pro and Business plans will be shared across ChatGPT and Codex, its coding agent. Usage will be measured in tokens, and “instant chat will not draw from your usage.” OpenAI hasn’t given a start date or allowance sizes by plan, TokenPost reports.
Why it matters: Chatting and coding used to be two separate habits. Soon a long Codex session will leave less room for everything else you do in ChatGPT, and the reverse. You’ll see your combined remaining usage under Settings → Usage, and at the limit you can wait, upgrade or buy credits. On Friday we covered OpenAI scrapping its ChatGPT Pro cut. This is the next chapter.
What everyone’s saying: The Hacker News thread is running hot, with 106 points and 48 comments when I read it. One commenter says Claude is already ahead on coding and that the merge will push non-coders to switch too. A researcher says the thing he pays OpenAI for is that Pro-tier chat and Codex are billed separately, which suits long math reasoning, and that he’ll “see once this transition actually happens.”
My read between the lines: OpenAI says it expects most users won’t wait for resets more often than they do now. That sentence is carrying the whole announcement, because there are no allowance numbers to check it against. The stated reason is bringing Work’s agent features into the main ChatGPT experience, which makes ChatGPT an agent product with a chat window, billed like one.
📖 Further reading: OpenAI Codex: Apache-2.0, 120,183 Stars, and the Bill That Isn’t in the Repo — Our Codex breakdown: the client is free, and what you can actually run depends on the plan, including an April cut OpenAI announced itself.
If your week now includes rationing one shared AI allowance, here is a thought: hand the grunt work to a coworker instead. Viktor is an AI agent that lives in your Slack and plugs into 3,000+ tools, then does the work: reports, dashboards, code and campaigns. Not a chatbot, a coworker. New readers get $50 off their first month. Hire Viktor →
DeepSeek Sketches an Agent That Never Logs Off BigGo Finance
What happened: On Saturday evening, DeepSeek’s Harness team published an article describing a “Super-agent”: one assistant that stays online, takes in messages from group chats, GitHub and email, and hands the work to separate worker agents. It also put an MIT-licensed prototype plugin on GitHub. BigGo Finance notes this is an engineering exploration, not a formal DeepSeek product.
Why it matters: The team’s argument is that agents are no longer limited by the model but by you: a person can usually follow only three to five active agent sessions at once. So a lightweight router sorts incoming work, workers keep their own context and tools, and a separate watchdog checks for tasks that stall or loop. DeepSeek says an internal instance already helps reproduce bugs and respond to code reviews.
What everyone’s saying: Coverage so far mostly relays DeepSeek’s own numbers. In its simulated tests, the 95th-percentile task time was 15.7 minutes against 29.5 for a conventional single-session setup, with cache-read tokens up about 37%. The team lists long-term memory, security and privacy, and human oversight as unsolved.
My read between the lines: Look at the test: about 300 simulated messages per run, roughly 20 of them real work requests, five runs each. That shows the plumbing keeps up, not that the fixes are any good. The detail I like is the watchdog. BigGo calls it an AI supervisor, so the system built to save human attention needed a manager of its own.
📖 Further reading: What Is ChatGPT Dots? — OpenAI’s own always-on agent, and why a helpful thing that works while you’re away gets harder to leave every day you use it.
A note from me: the daily Brief is free and always will be. If you want the longer, messier version of a story like today’s OpenAI one, members get the paywalled deep-dives plus the full archive. Become a member →
Four AI Labs Agree on One Keep-Out Line Engadget
What happened: Google, Anthropic, OpenAI and Microsoft committed on Friday to honor a new robots.txt directive that lets publishers opt out of generative AI training with one rule instead of one per company, Engadget reports. It comes from a proposal at the IETF, the internet standards body, written by Anthropic’s standards lead Kevin Kelley. Sites add a group with the user agent __usage_ai-training, then Disallow rules, with Allow lines for folders like a press kit.
Why it matters: Until now a site had to name each crawler and keep separate rules for every provider. The new token covers training only: it doesn’t block crawling, doesn’t change how a site shows up in search, and can’t undo anything already scraped. Anthropic has started honoring it, Microsoft begins February 1, 2027, Google says early 2027, and OpenAI says “the coming months.”
What everyone’s saying: OpenAI calls it a “voluntary effort” and says it “will not replace the controls we already provide through robots.txt.” Engadget notes Google will read the token as a block on Google-Extended, the crawler that gathers material for Gemini training. One explainer points out that it isn’t an official IETF standard yet.
My read between the lines: A sign on the gate, not a lock. Nothing in the announcement creates a legal duty, and for the next few months the practical effect for a publisher is close to zero. The Google detail is the telling one: the new shared line gets treated as the Google-Extended block publishers could already set. One line of intent is tidier than four rule sets, and that’s the real win.
📖 Further reading: Google’s Invisible Axe: The Silent Killer — Not about training data, but about what happens when Google’s rules apply to you and its support doesn’t answer: Google unlisted our business and every appeal went nowhere.
Viral Anthropic Claim Doesn’t Check Out X
What happened: A post from @halvenruns, at about 1,600 likes when I read it, credits an “Anthropic Research Lead” with saying “prompting is basically over,” that “99% of our engineers already run swarms of 300+ self-improving agents,” and that “now everyone is shifting to graphs,” all in a 20-minute talk. A day later the account posted a new version of the same pitch with 95%, no swarms of 300+, a ten-minute video, and an “Anthropic engineer.”
Why it matters: Lines like this get screenshotted into slide decks. Here is what I could find behind it. The Chinese-language account Mai Yang says the 20-minute talk is by Theo Chu, an Anthropic research product manager, at Code w/ Claude Tokyo, covering how Claude’s capabilities are rising, evals, shrinking scaffolding, auto mode and closing the agent loop. The ten-minute “empty terminal” clip, posted to YouTube on October 25, has a transcript that is a Claude Code product manager announcing general availability and the Claude 4 models. I couldn’t find the 99% or the 300-agent figure in either.
What everyone’s saying: The real-world version of the claim is that people are supervising agents, not writing code. Forbes reported on October 26 that Claude now writes 90% of Anthropic’s code. The sharpest reply under the post is shorter: “The guide is still a prompt.”
My read between the lines: If Mai Yang’s summary is right, the advice from the stage was to shrink the scaffolding as models get stronger, which is close to the opposite of “everyone is shifting to graphs.” I haven’t watched the Tokyo talk myself, so treat that as her description. Whether agent graphs are the next thing is a fair question. One unsourced percentage from an account whose numbers changed in a day isn’t evidence either way.
📖 Further reading: The 4 New Skills of AI (Part 1): Escaping the Context Trap — Our earlier take on what replaced prompt tricks: context engineering, through Nate Jones’s four-skills framework.
OpenAI Trims Its Funding Round to $20B Trending Topics
What happened: The Financial Times reported that OpenAI cut the target for its current round by $10 billion, to $20 billion, and now seeks a $1.25 trillion valuation, down from $1.4 trillion. The FT story is paywalled, so the link goes to Trending Topics’ summary.
Why it matters: At that price OpenAI would still be the most valuable private company in history, and $20 billion is still one of the largest rounds ever. Reports cited by Trending Topics put third-quarter revenue growth at 77% (unaudited). The cut lands as tech stocks wobble over AI spending, and as Anthropic is reportedly preparing a November listing at around $1.5 trillion. On Friday we covered Anthropic as SpaceX’s biggest customer.
What everyone’s saying: Coverage reads it as investors getting pickier: some trimming their allocations, a selloff in tech stocks, and a first close that could come in below $20 billion, according to reports. OpenAI has also pushed its own IPO plans to 2027.
My read between the lines: My guess, not reporting: when capital gets pickier, everyone starts rationing, and that shows up as shared pools, tighter limits and fewer free tokens. Story one in today’s Brief might be the same pressure arriving from the other end. The headline number is smaller, but the revenue growth reportedly isn’t.
📖 Further reading: Everyone’s panicking about the Anthropic IPO. They’re wrong. — As OpenAI and Anthropic chase public money, this post argues the real risk is how much of your workflow lives inside one vendor.
That’s your AI Brief for Sunday.
—Nicholas from Artificially Intimidating
