Seven stories for Tuesday, October 13. Meta ships Muse Wonder and calls it frontier, NVIDIA and Cisco redraw pluggable optics at 400Gb/s per lane, Codex Day 2 lands four friction fixes, Microsoft Research grades agents on finished state, the IMF sizes AI against global growth, OpenAI retires the first GPT-4o API snapshot, and three fired safety researchers answer back.
Meta puts a new flagship on the board: Muse Wonder
Meta released Muse Wonder and its fuller sibling WonderFull on Monday, and the claim is blunt: these are frontier models, built for personal and professional agent work. Zuckerberg framed the launch as the payoff of the fourteen months since Meta Superintelligence Labs was reorganized, with Muse Spark as the first series and Wonder as the real step up. Meta AI head Alexandr Wang told reporters these models can compete with ChatGPT and Claude, especially on personal and professional agent tasks, and invited users to judge for themselves.
Two capabilities carry the pitch. Active Memory keeps important context across conversations and pulls it back in when a new task starts, so the model does not need a fresh briefing every time. Active Focus keeps pushing a complex goal forward, trying other routes when one path stalls and adjusting to new information. On Meta's internal MemoryBench, which asks models to recover key facts from multi-turn dialogues of 64,000 to 100,000 tokens while ignoring noise and resolving conflicting updates, Wonder scored 85.6 against 81.4 for GPT-6 Astra and 81.5 for Opus 5.5. On SWE-Marathon, a benchmark for long-horizon software engineering, WonderFull passed 57.5% and Wonder 53.1%, ahead of the three competitors Meta listed in its comparison.
The business model is as interesting as the scores. Wonder ships through the Meta Model API at $4 per million input tokens, $0.20 for cached input and $20 for output, and WonderFull arrives through the MuseCode coding tool inside $50 and $200 subscription tiers. Using Wonder inside the Muse assistant requires the $20 or $100 monthly plan. Zuckerberg said on the Cheeky Pint podcast that running a gigawatt-scale data center costs roughly $15 billion a year on top of $50 to $60 billion in upfront construction, and that subscriptions, API access and enterprise deals are how that spend turns into revenue. Meta is betting that people will pay for an agent that actually finishes things, not just answers.
— Meta · Bloomberg
🔗 Meta AI · Bloomberg via Sina
NVIDIA and Cisco redraw the plug: USFP goes to 400Gb/s per lane
NVIDIA and Cisco announced USFP, the Ultra-Dense Small Form-factor Pluggable, on Monday. It is the first pluggable optics module designed for 400Gb/s-per-lane electrical signals, and it exists for one reason: AI factories keep hitting the point where adding compute means adding network tiers, and every extra tier costs latency, power and money. The first planned transceivers pack 16 full-duplex lanes into an OSFP-sized footprint, with a path to 32 lanes and 12.8Tb/s of aggregate capacity per module.
The numbers are the story. Against today's 200Gb/s-per-lane pluggables, USFP delivers four times the bandwidth density and about 1.3 times the power efficiency, so operators can connect more 1.6Tb/s endpoints without stacking more switch layers. A new two-dimensional array connector with a two-step insertion design protects signal integrity and keeps insertion force predictable, and the module dissipates up to 100 watts without a dedicated embedded cooling circuit. NVIDIA's Gilad Shainer put it simply: building the largest AI factories starts with rethinking the smallest connections.
The ecosystem play matters as much as the spec. TE Connectivity and Amphenol are building cages, connectors and modules, and the two companies plan to hand USFP to a community-led multi-source project as an open industry specification, extending work that keeps NVIDIA Spectrum-X and Cisco Silicon One networks interoperable. If the industry adopts it, pluggable optics gets another generation of life; if not, this stays a two-company standard. Either way, the message is that the network, not the GPU, is where AI factory scaling hurts now.
— NVIDIA · Cisco
🔗 NVIDIA Newsroom · Cisco Blog
Codex Day 2: OpenAI ships four fixes for agent friction
Day 2 of the Codex 28-day pledge brought four updates at once, and none of them chase benchmark numbers. The first is Auto-review, the mode previously known as Approve for me, now free for everyone who signs in with a ChatGPT account and no longer charged against usage limits. A second agent watches the main one and flags high-risk actions and moves that drift from the original intent. When an agent runs for forty minutes instead of four, clicking approve on every step stops being a safety feature and becomes the bottleneck, and this is OpenAI's answer to that middle ground.
The second change hits the API. Five usage tiers collapse into three: Build at $5, Launch at $100 and Grow at $500 in cumulative spend, with the top tier's threshold cut in half from $1,000 and automatic promotion once you cross it. Rate limits become the practical ceiling when an application scales from test to production, and OpenAI chose to shorten that path rather than add another layer of rules. The third update brings the Meetings plugin into ChatGPT on macOS for Pro and Business users in beta: it records, summarizes and files decisions and action items into Spaces, where they become inputs for the next round of project work.
The fourth is the one developers have waited on since DevDay. Decisions API, previewed on September 29, is now in public beta. Driven by GPT-6 Luna, it returns Predicates, Choices or Scores instead of generated prose, at up to ten times the speed of the Responses API, and it is aimed at request routing, tool selection, classification and pre-call risk checks. OpenRouter already lists it at $0.10 per million input tokens with no output charge. Taken together, the four updates describe a clear thesis: agents can already do the work, and the remaining friction lives in approval prompts, tier paperwork, meeting context and overkill inference.
— OpenAI · Tibo Sottiaux
Microsoft's Thinkingbox grades agents on finished state, not good manners
Microsoft Research released Thinkingbox, a sandbox and benchmark built around a simple complaint: most agent benchmarks check whether the model called the right tool, when what actually matters is whether the job got done. The suite contains 507 policy-conditioned workflows across retail, hospitality, auto insurance, neobank IT support and consulting, and every one is scored by executable checks against the terminal backend state, not by reading the agent's reply.
The results explain why this matters. The strongest model reached 65.36% pass@1 but only 25.25% when each workflow is attempted twenty times. That gap is the finding: many failures still produce clean terminations and plausible-looking state changes while missing the required outcome, which is exactly the kind of error a reply-based evaluation never catches. The workflows stress multi-turn information gathering, adherence to written policy and persistent state transitions, the dimensions that current benchmarks mostly ignore.
For teams shipping agents into real operations, the repo is worth a weekend. Running your own evaluation harness against these workflows will show quickly whether it measures intent or outcomes, and the pass^20 numbers are a sobering baseline for anyone promising reliability to a customer. Benchmarks like this are how agent engineering grows up: you cannot fix what you refuse to score.
— Microsoft Research · arXiv
IMF: AI investment is holding up global growth, and the bill comes later
At the IMF and World Bank annual meetings in Bangkok, Managing Director Kristalina Georgieva said heavy investment in AI infrastructure is keeping global growth near 3%, with Asian economies among the main beneficiaries as suppliers of hardware and equipment. It is a rare macro note in a policy discussion that usually centers on risk, and it matches what chip and data center earnings have been saying all quarter.
The caution arrived in the same speech. The IMF estimates AI could displace or downgrade about 40% of jobs over time, and Georgieva warned that the technology poses a disruptive threat to both employment and tax bases. Growth today is being pulled forward by capital spending; productivity gains tomorrow depend on whether economies retrain workers faster than AI absorbs their current tasks. Bangkok's message was that both numbers are real and policy has to handle them together.
For investors and operators, the read is straightforward. The compute buildout is now macroeconomically significant, which means it will show up in growth statistics, trade balances and labor data, and it will attract the kind of scrutiny that follows anything that big. The companies building AI factories should expect the conversation about power, jobs and taxes to move from op-eds into actual policy.
— IMF · Reuters
OpenAI retires the first GPT-4o API snapshot on October 23
OpenAI will deprecate the earliest GPT-4o API snapshot on October 23, according to a notice picked up across developer channels on Monday. The model itself was removed from ChatGPT back in February, but the API snapshot lived on in production code, and now it has roughly ten days left. Applications that pinned an early snapshot for cost, latency or behavior reasons need to migrate or accept a silent switch.
What makes the story more than routine housekeeping is the reaction. Petitions and open-source reimplementation requests have been circulating since February, and the retirement notice has given them a fresh push. Developers argue that a model embedded in long-lived workflows is not just a product SKU; it is a dependency, and dependencies deserve migration paths measured in quarters, not days.
The practical advice is unglamorous: pin your current snapshot, diff your outputs against the replacement, and budget for prompt retuning, because small behavioral shifts in a model can move an entire product's metrics. Model churn is now a normal operating cost of building on frontier APIs, and this retirement is a reminder to treat it like one.
— OpenAI
Three fired OpenAI safety researchers publish an open letter
Three OpenAI safety researchers fired on October 1, Tomek Korbak, Jasmine Wang and Mikita Balesni, published an open letter this week pushing back on their dismissals. They argue they always acted within OpenAI's own policies and suggest the company's norms around handling research information are shifting under them. OpenAI, in a statement to TechCrunch, reaffirmed that the three had shown a pattern of misconduct in how they handled research information.
The letter matters because of who is signing it and when. It follows the departure of safety reports lead David Robinson, who wrote earlier this month that the culture is broken, and it lands while OpenAI is pitching enterprises on trust and governance. A safety team in open conflict with its own employer is a hard look for a company whose sales pitch is that its safeguards are the product.
Two things are worth watching. First, whether the dispute stays a personnel matter or turns into a documented pattern that regulators and enterprise buyers start citing. Second, whether other labs treat this as a warning about how they handle internal safety dissent, because the alternative is watching the same story repeat with different names.
— OpenAI · TechCrunch
KD Agentic · AI Daily Digest
Top comments (0)