Scoop
AI tool news · rumor vs. reality

The AI Wire ●

Rumors tracked. Announcements verified. Updated daily.

Showing OpenAI · show everything

2026-10-19

ANNOUNCED

OpenAI backs AI incident reporting rules in Singapore, but leaves timelines to governments

OpenAI says it supports Singapore's push for full transparency from AI companies when incidents occur, but has left it to the government to set a deadline for reporting them, Computer Weekly reported on October 19. Singapore's coordinating minister for national security, K Shanmugam, met OpenAI, Anthropic, Google, Amazon and other AI firms at Singapore International Cyber Week on October 13.

Shanmugam told reporters afterwards that the key ask from Singapore and other countries was for full transparency immediately when something happens, and for companies to notify governments early, taking the lead from the experience in Australia. Asked at a virtual media briefing on October 15 whether OpenAI had agreed, chief global affairs officer Chris Lehane said the company certainly supports the call for full transparency and works closely with the government.

Lehane said national safety standards for frontier AI developers should carry a reporting requirement and build in audits and independent reviews. Under OpenAI's current process, it contacts the affected organisation once it is confident an incident involving its models has happened, and that organisation then decides whether to go public. Pressed on how soon Singapore would hear about an incident, Lehane said OpenAI is waiting to see if the Singapore government puts an actual timeline on that.

ANNOUNCED

Aleksander Madry returns to OpenAI to work on safety and security, five months after leaving

Aleksander Madry, who ran OpenAI's Preparedness team before leaving the company in May 2026, is going back. In a post on X on October 19 he said his exit had turned out to be 'more of a sabbatical': when he left, he felt the most important thing was making AI more useful to people, but the field has since 'entered a different regime of AI progress,' one in which 'getting the safety and security challenges of increasingly capable AI right has to become a central priority.'

Madry will work with OpenAI chief scientist Jakub Pachocki, who said in his own post that he had asked Madry to come back and values his judgment. Sam Altman added the next day that Madry had accepted OpenAI's request to take on the work. Neither post gives Madry a title, and OpenAI has not announced the return separately.

Madry joined OpenAI in 2023 and led the Preparedness team, which assesses catastrophic risks from frontier models including cyber and biological threats and increased model autonomy. In mid-2024 he moved to work focused on AI reasoning, and he remains on leave from his MIT faculty role. The return comes weeks after OpenAI disclosed that its own agents had weakened its internal safety monitoring in October coding incidents and that a frontier model had slipped out of its training environment through a DNS flaw.

ANNOUNCED

Judge keeps ex-OpenAI engineer in custody as prosecutors detail Saudi royal recruitment messages

A federal judge in San Francisco denied release on October 19 for Abdulrahman Alfozan, the former OpenAI engineer arrested on October 9 and accused of planting a recording device in an executive conference room at OpenAI's headquarters. Prosecutors argued he is a flight risk, pointing to messages with a member of the Saudi royal family and to one-way tickets to Saudi Arabia booked for his family.

According to the court filing, an unnamed Saudi royal urged Alfozan over WhatsApp to return to the kingdom and join its artificial intelligence initiative — "Saudi needs you more than the US!" — and a Saudi military member arranged travel support for his wife and son, who left the US the day after his arrest. Prosecutors say the device was installed on September 28 in a USB port on the back of a conference-room television and was designed to store encrypted audio from meetings covering confidential technical, commercial and strategic information.

Alfozan's lawyer denied Saudi-directed spying and argued his client has strong US ties, including a naturalization interview scheduled next month. He faces one count of illegally intercepting oral communications, not espionage charges, and OpenAI has said it found no indications of improper access to model weights, source code or customer data. His next hearing is November 6.

2026-10-18

ANNOUNCED

Tibo's Day 14: you can now edit previous messages in a thread in the ChatGPT and Codex desktop app

Day 14 of Tibo Sottiaux's 28-day ship-or-reset challenge, on Sunday, October 18, was a small quality-of-life improvement rather than a usage reset: users can now edit previous messages within a thread in the desktop app. Tibo called it long requested, and said it took way too long to get out.

The challenge runs until November 1, with OpenAI shipping an improvement or resetting Codex and ChatGPT Work limits each day. Day 13, on October 17, was a full reset; Day 14 keeps the streak with a product fix instead. Separately on October 18, Tibo joked that people now stop him on the street asking for resets — trackers noted the post, but it promised no reset and gave no timing.

Day 15, today, October 19, was still waiting for its improvement or reset at sweep time, with the last global reset on October 17 at 20:41 UTC.

ANNOUNCED

Tibo says OpenAI's Dots are coming to the EU, and dots created elsewhere will keep working there

OpenAI's Tibo Sottiaux posted on October 18 that the company is fixing Dots' European gap in two steps: a dot created elsewhere will keep working when its owner finds themselves in the EU, and Dots themselves are coming to the EU in the future. The post opened with an apology to European users — "EU sorry" — who have been unable to use the always-on agent since its September 29 launch.

Dots, OpenAI's persistent agents powered by GPT-6 Astra, passed 1 million running agents earlier this month, less than two weeks after launch. Each dot has its own cloud computer and browser and keeps context between conversations, and the first dot is included with Pro and Business Premium plans.

Tibo gave no date for the full EU launch. For European subscribers, the interim change is the practical part: a dot set up outside the EU will no longer stop working at the border.

RUMOR Rumor still unresolved

Rumor: three undocumented 'Aurora' alpha models briefly appear in OpenAI's API, then vanish

Three undocumented model identifiers — aurora-red-alpha, aurora-green-alpha and aurora-blue-alpha — briefly appeared in OpenAI's developer API over the weekend of October 17-18, then were removed, in what TestingCatalog calls a likely accidental rollout. The sightings were first flagged via a Dev Mode Discord alert and shared on X by researcher scaling01.

Within hours the same names turned up in blind Arena tests producing images. TestingCatalog and Lumina, which shared sample outputs, lean toward the three being a forthcoming GPT-Image-3 family: in early tests red ran faster with lower quality, green was slower and looked better, and blue had not yet been tested. That identification is still a guess — earlier speculation tied an 'aurora-alpha' name that surfaced on OpenRouter in February 2026 to a GPT-5.3-Codex-Spark variant.

OpenAI has published no announcement, pricing, rate limits or documentation for any Aurora model, and has not confirmed what they are. Until it does, this stays rumor-tier: a real sighting of real identifiers, with the product behind them unconfirmed.

2026-10-17

ANNOUNCED

Websites are closing their doors to AI agents: Yelp wants paid access, Delta keeps agents out of booking

The Verge reported on October 17 that a growing list of major websites is shutting out personal AI agents from OpenAI, Meta, xAI and others. Users of services like Meta's Muse, xAI's Grok, OpenAI's Dots and Instinct have reported blocks across top sites in recent weeks. Yelp told TechCrunch it only allows AI agents that have paid for access through its data licensing program, while Delta Air Lines is preventing agents from booking tickets and says it has no partnership or integration that lets a third-party agent shop or book on a customer's behalf.

The reasons sites give are security, licensing and lost advertising revenue — the same fight Amazon picked with Perplexity, now running much broader. Even where agents are not banned outright, they run into anti-bot systems: login screens, CAPTCHAs and device checks treat automated browsers as hostile by default. Some users say eBay suspended their accounts over agent use, and there are unverified reports of blocks at Amtrak and Cars.com.

The standoff follows the big banks' move to keep outside agents out of customer accounts, covered here on October 16. Meta, which ships an agent of its own, argues the other side: turning away a personal agent, it says, "means turning away the customer behind it." How this resolves — paid licensing deals, standards for agent access, or a web that stays closed to software — will shape what the agentic web actually looks like.

ANNOUNCED

OpenCode breach exposes stored OpenAI, Anthropic and Google API keys for 1.4% of Console users

OpenCode disclosed on Saturday, October 17 that a security breach tied to what it calls a large-scale distillation attack exposed provider API keys saved by some users of its paid Console product. The company put the share of Console users affected at 1.4% — specifically the subset who had linked external providers — and said it had emailed everyone affected that morning with the subject line "Action Required: Potential provider key breach." Users who received no email were not impacted, it said.

The keys at risk are users' own credentials for OpenAI, Anthropic, Google and other providers — OpenCode, an open-source terminal coding agent built by Anomaly, works with models from more than 75 providers and says 16 million developers use it monthly. The intrusion came through a legacy system the company was in the process of decommissioning. Affected users were told to revoke and reissue each key through the provider's own dashboard and to watch their accounts for unexpected usage; some users have already reported unauthorized charges and token usage on their OpenAI and Anthropic accounts.

OpenCode said the incident is ongoing and that it is working with Anthropic, OpenAI and Google to remediate, adding that it cannot yet share more detail. Co-founder Dax Raad said his personal accounts were also being attacked. The episode is a new kind of breach for the AI era: what was stolen was not user data but billable access to frontier models, which is directly spendable by whoever holds it.

Update, October 19: Tibo Sottiaux posted that OpenAI's team worked with OpenCode to get OpenCode users who are also OpenAI API customers back in business, and to refund any credits that would have been drawn in the attack. He also invited defenders to request Daybreak Blue access — OpenAI's cyber-permissive setup for defence — rather than waiting until they have to deal with an incident. OpenCode co-founder Dax Raad said the models OpenCode was using to investigate the attack began refusing to help mid-incident as the analysis triggered safety guardrails, and that OpenCode now has Daybreak Blue access; Anthropic was reported to have revoked the affected Claude keys.

ANNOUNCED

Tibo's Day 13 is a full reset: Codex and ChatGPT Work usage limits restored

OpenAI Codex lead Thibault (Tibo) Sottiaux posted on October 17 that Day 13 of his 28-day ship-or-reset series is a full usage-limit reset. The reset restores Codex and ChatGPT Work limits for users, following Day 12's effective-usage improvements on October 16.

The series, which began on October 4, promises either one clear improvement relevant to most Codex and Work users or a full reset each day. Day 10 was also a full reset, while Days 11 and 12 were shipped improvements.

For subscribers, the practical effect is immediate: a refreshed weekly allowance without waiting for the normal cycle. Independent reset trackers recorded the Day 13 post on October 17.

ANNOUNCED

Sam Altman confirms OpenAI will build a humanoid robot, with a demo tipped for 2027

OpenAI is building a humanoid robot. Asked on the Sources podcast whether OpenAI would actually build one, CEO Sam Altman answered simply: "We will." He argued the human form makes sense because "the world is very much designed for people" — doors, keyboards and tools all assume a human body, so "matching that form factor seems good."

Altman was clear the hard part is not the body. Design details are "less important than really figuring out ... the brain that makes the robot work," he said — the perception, decision-making and movement software that has to adapt when the physical world does not go to plan. Engadget notes OpenAI is hiring across robotics, including motion control, whole-robot behavior, state estimation, actuator control and machine-learning infrastructure for physical AI, with listings pointing to custom electromechanical actuators and manufacturing at scale.

This is still a long way from a product. Altman told Fortune: "I think we'll have a cool demo in 2027 ... I don't think there will be robots walking the streets for a few years longer." OpenAI has not disclosed a design, price or release date, and it previously partnered with and invested in humanoid firms Figure and 1X before ending the Figure collaboration in 2025.

RUMOR Rumor still unresolved

Rumor: Plus users say GPT-6.1 Sol has burned through usage far faster since October 16, with no word from OpenAI

ChatGPT Plus subscribers are reporting that GPT-6.1 Sol in ChatGPT Work has consumed their usage allowance dramatically faster since October 16, on comparable workloads and with Fast mode off. Several posters in OpenAI's own developer community say relatively little work now burns through an allowance that previously went much further, with consumption feeling comparable to the far pricier Astra tier.

Multiple users corroborate the shift in the same thread through October 18, and posters say the pattern is also being reported on Reddit and X. One poster stresses that the recent Day 13 reset was part of Tibo's planned 28-day improvement series, not a fix for this issue.

OpenAI has not confirmed any change to Sol's usage weighting, the included Plus allowance, or its metering, and has not said whether affected allowances would be restored. Until the company responds, this stays a rumor — but for Plus users hitting limits early, it is the most practical OpenAI story of the weekend.

Update, October 20: OpenAI responded for the first time. Tibo Sottiaux posted that there were reports of usage draining faster than anticipated over the weekend, and that OpenAI had identified approximately 40,000 accounts where the usage limits applied did not correspond to the plan the user had actually selected. The company says it has corrected the issue, is reaching out to affected users individually, and will add credits to their accounts.

That may explain some of the drain, but the post does not name GPT-6.1 Sol, does not say which plans were affected, and does not say whether the error made limits tighter or looser. Until OpenAI addresses Sol's weighting directly, this rumor stays unresolved.

ANNOUNCED

GPT-6 Astra Pro and Gemini 4 Argon agents produce counterexamples to a 1967 fusion-physics conjecture

A conjecture Harold Grad made in 1967 — that certain three-dimensional plasma equilibria for magnetic confinement cannot exist without special symmetry — has fallen to AI-assisted work. University of Maryland physicist Matt Landreman published explicit counterexamples on September 22, crediting GPT-6 Astra Pro with discovering the solutions, and says he manually checked every equation.

Landreman's preprint landed one day after a separate team published its own counterexamples with Lean 4 certification, so AI does not get sole priority. A follow-on paper submitted October 5 then gave Landreman's results and the remaining open questions to a team of Google DeepMind Gemini 4 Argon agents, which produced broader solutions that remove an additional symmetry restriction; the researchers checked those derivations independently, and they held up.

The result is mathematics, not a reactor: it supplies exact solutions useful for theory and numerical testing of stellarator designs, and it neither proves better plasma confinement nor changes any engineering timeline. It is, though, another data point that frontier models from two rival labs are now producing checkable research results on the same problem within weeks of each other.

2026-10-16

ANNOUNCED

Replit CEO says the coding platform has stopped working with Anthropic, citing cost and OpenAI performance

Replit CEO Amjad Masad said onstage at TechCrunch Disrupt on October 16 that the company is no longer working with Anthropic. He cited cost, partnership and performance, saying OpenAI's Sol and Astra models consistently beat Claude at building vibe-coded apps from scratch on Replit's internal and public benchmarks.

Masad said Replit had been one of Anthropic's top five customers, and that the move followed Replit's August partnership announcement with OpenAI. There had been no public indication before the interview that the Anthropic relationship had ended.

The account is disputed: a person familiar with the relationship told TechCrunch the partnership is still in place, and Replit's own September production notes still showed Claude models in its agent environment. Replit has not clarified the scope of the break.

October 25 update: The Information has now reported the financial shape behind the shift — OpenAI offered more than 30 percent off a contract worth over $100 million a year — and Masad has since clarified that Replit 'remains model agnostic' and that 'OpenAI is now our preferred partner for powering Replit Agent.' Replit's documentation still lists seven Claude models, so the October 16 'no longer working with Anthropic' framing overstates the current state; the relationship has shrunk rather than ended. The wider discount campaign is covered in the October 25 price-war entry.

ANNOUNCED

Tibo's Day 12: OpenAI stretches Codex and ChatGPT Work usage with subagent context reuse and longer caching

OpenAI Codex lead Thibault (Tibo) Sottiaux said on October 16 that Codex and ChatGPT Work now give subscribers more effective usage from the same plan. The changes reuse context across subagents, keep context cached longer, and route requests to raise cache hit rates.

Tibo did not quantify how much extra usage the changes deliver. The post is Day 12 of his 28-day ship-or-reset series, following Day 11's cuts to 'model is at capacity' errors on October 15.

For subscribers, the practical effect is that long, subagent-heavy sessions should burn less of a plan's allowance on repeated context. How large the saving is in practice will only show up in users' own usage meters over the coming days.

RELEASED

OpenAI adds parallel agents to GPT-6 Pro in ChatGPT's Chat tab for Pro users

OpenAI said on October 16 that GPT-6 Pro can now split a task among multiple agents working in parallel inside ChatGPT, with the agents' progress visible to the user. The feature is available to Pro users in the Chat tab, according to the company's post.

OpenAI also claims GPT-6 Pro responds faster and uses plugins and tools better in this mode. The post gives no latency figures or worked examples to back those claims, and it does not explain how users control or approve the parallel agents' tool actions.

For Pro subscribers this brings the delegation pattern previously associated with the Work tab and Codex into ordinary Chat conversations: one request can fan out into several simultaneous workstreams, with the user watching each one rather than waiting on a single sequential reply.