The AI Wire ●

A model OpenAI has never announced is turning up in its own usage accounting. Over the weekend of October 31 to November 1, several Codex users posted screenshots of their usage analytics listing a model called gpt-6.2-astra alongside GPT-6 Astra, the flagship OpenAI launched on September 3. TestingCatalog, reporting on November 2, found the new ID only on the October 31 bar of each breakdown, at shares that vary widely by account — 1.6% of one user's week, 19.8% of another's, and 37.7% of a single day for a third.

The model picker still says GPT-6 Astra, which points to quiet server-side routing — an A/B test or the start of a staged rollout — rather than a launch anyone chose. Watchlist account Token Gremlin (@TokenGremlin) shared a raw response event whose model field reads "gpt-6.2-astra" and called it official; that is strong evidence the ID is live on OpenAI's servers, but it is not an announcement. A separate review by VanData scored the Astra screenshots the strongest evidence of the weekend's leaks, while noting they cannot be traced to a full request.

Nothing official backs the name up. Checks on the morning of November 2 found gpt-6.2-astra in none of OpenAI's public places: not the API model catalog, not the API changelog (whose latest entry is gpt-6-rosalind on October 30), not the Codex changelog, and not the public models.json, which still lists five GPT-6 family slugs. Claims that 6.2 is more powerful, cheaper or faster are unverified. The context makes a successor plausible — OpenAI shelved GPT-6.1 Astra in late September after internal testing raised concerns, so a jump straight to 6.2 would fit a fixed, retrained model — but OpenAI has confirmed no name, price or date. This stays rumor, unresolved.

A reference to an unannounced Claude Mythos 5.5 has been spotted on Anthropic's official Mythos webpage, TestingCatalog reported on November 1. The line describes it as “Our most capable model class for cybersecurity and biology research.” The mention is not present in the page's October 23 snapshot, so it was added in the last few days — but it is only a version number: no specifications, pricing, release date or announcement accompany it.

Alongside the sighting, multiple reports say Anthropic has been A/B testing updated Claude Fable 5.5 checkpoints with selected users, with early impressions described as state-of-the-art. Those comparisons are anecdotal and no public benchmarks exist. Anthropic released the previous Mythos and Fable variants together — Mythos 5.1 restricted to verified cybersecurity and life-sciences researchers, Fable 5.1 the same underlying model with extra safeguards for general use — so a paired launch is plausible, and some testers speculate a launch could come as early as Tuesday. That timing is speculation, not a schedule.

This stays a rumor: Anthropic has confirmed nothing, and a website string is not a launch. It is, however, the strongest new data point yet for the Wire's long-running Fable 5.5 story, first logged on October 13 from Azure and LiteLLM listings — that rumor remains unresolved. The sighting also lands a week after Anthropic filed for a Nasdaq listing under the ticker ANT on October 26, when a major model release would draw extra attention.

Update, November 2: the 5.5 name is gone again. ArtificialWatch reported the Mythos page header read Claude Mythos 5.5 at about 15:30 UTC on November 1 and was back to 5.1 by 17:30 UTC, and a November 2 check found no mention of 5.5 at all. A Van Data Team trace of the weekend's paired leaks also weakened the Fable half of the story: the circulating Fable 5.5 "specs" — a 1M-token context and 128K-token output — were copied from Fable 5.1 into a price list and removed a day later. Anthropic still says nothing, and no model has been announced: this rumor stays unresolved, and thinner than it looked on Sunday.

A screenshot of what is described as an internal model-tracker bot, logged on October 28 and shared in X discussions on October 29-30, shows an entry named gpt-6.2-betelgeuse tagged INTERNAL. Commentator Chubby (@kimmonismus) posted 'GPT-6.2 bel incoming' alongside it, with the caveat that he could not confirm it. A compilation of the leaks counts several users posting similar tracker screenshots around October 30, though the provenance of the images is unverified and no authenticated API response sits behind them.

The name connects to the August Bel rumor already on the Wire: a reported pretraining run of more than 10 trillion parameters, said to be the base for whatever follows GPT-6. Other commentators argue a new pretrain would more likely ship as GPT-6.5 or GPT-7 than as a 6.2, and Wccftech's separate reading — that OpenAI's banked resets hint GPT-6.1 Astra lands next week — is speculation on top of a model OpenAI cancelled on September 28, not a reversal of that decision.

On November 1 a thread on r/singularity titled 'OpenAI is testing GPT-6.2 Astra' added another screenshot, with commenters debating whether it shows the same model as Betelgeuse or a version of Astra. A review by Kingy.ai on October 31 found no GPT-6.2 entry in OpenAI's model directory, model release notes or API changelog. OpenAI has not confirmed the name, capabilities, pricing or any release date — everything here remains rumor.

OpenAI has cut the target for its latest funding round by $10 billion, the Financial Times reported late on October 30, citing people familiar with the matter. The ChatGPT maker is now seeking about $20 billion at a $1.25 trillion valuation, down from the $30 billion at a $1.4 trillion valuation it was pitching last month. OpenAI set a Friday deadline for investors to commit, but the first close is expected to come in below even the reduced $20 billion after some investors cut their allocations.

A consortium of United Arab Emirates investors, including state-backed fund MGX, is expected to be the largest participant, with OpenAI getting an option to lease newly built computing capacity in the region as part of the deal. SoftBank, Sequoia Capital, Coatue, Founders Fund and Andreessen Horowitz are also expected to take part, and wealthy individuals would be offered a later retail tranche at the same $1.25 trillion valuation.

This revises the bridge round the Wire covered as a rumor on October 22, then reported at $30 billion and a $1.25 trillion valuation. The cut lands in the middle of a sharp AI-led stock sell-off and just as Anthropic's public listing approaches. OpenAI, which raised $122 billion in March at an $852 billion valuation, did not comment on the report, and the terms remain unconfirmed — treat the new figures as rumor-grade until the round closes.

Meta has been attaching cryptographic signatures to a growing number of web requests from its Muse personal agent and its Meta-WebIndexer crawler since around October 12, according to Jérôme Segura, VP of Threat Research at bot-management company DataDome, who described the observation in a LinkedIn post on October 30. The signatures use Web Bot Auth, a protocol that lets a website verify that an automated visitor really comes from the company it claims.

Segura was careful about the limits of what he saw: there has been no public or official announcement from Meta, the signed requests are still a relatively small share, and early signed traffic may have run under a Meta-ExternalTest user-agent string. Meta's public crawler documentation, as of October 31, lists five automated agents and mentions neither Web Bot Auth nor a test agent. DataDome says it now validates the signed requests for its customers.

Signed agent identity is becoming a live issue as personal agents like Muse browse and transact on users' behalf: sites want a way to tell a genuine Muse visit from an impersonator. Meta's revised crawling terms are due to take effect on November 20. Until Meta documents the change, this stays rumor-grade — a single researcher's observation, however credible the source.

Installer files labelled Grok Bot 1.0.0 have appeared on Cursor's download server, grokbot.guru reported on October 29. The site checked the Mac installer for Apple silicon on Thursday morning with a HEAD request — which reads a file's details without downloading it — and the server returned the 155.6 MB .dmg, dated October 27 at 6:14 p.m. CT. A check of the Windows x64 installer the same morning also returned a working response.

Nothing official matches it yet. SpaceXAI hasn't announced 1.0.0, the official Grok Bot changelog has no entry for it, and the newest official release there is still 0.78.1, released October 27, which added shopping cards and subscription templates. What the 1.0.0 version changes, and when it will be released, are not known. Kevin Logan posted on X on October 27 that "Grok Bot 1.0 Stable just showed up on the download server," and asked the next day whether anyone had seen it pushed out to users yet.

grokbot.guru advises waiting for the update to arrive through the app's Updates pane rather than installing 1.0.0 from a direct file link before SpaceXAI releases it. This stays a rumor until the changelog or an announcement lands.

An October 30 follow-up from TestingCatalog adds colour but no confirmation: it reports SpaceXAI is preparing Grok Bot 1.0.0 as the first stable release, with the build already downloadable ahead of an official rollout, and spots features in development alongside it — a more direct Microsoft Teams integration, a dedicated Tasks tab, a Texting tab in Settings with permissions to read and send text messages, and early signs of Discord support. None of those features has a confirmed timeline, and there is still no official 1.0.0 announcement or changelog entry, so the rumor stays unresolved.

An October 31 TestingCatalog daily brief goes a step further, describing Grok Bot 1.0 as 'the first stable build' that is out for download, and adds two more sightings: Grok Bots rolling out to X Chat, so users can message their bots like any contact without leaving the X app, and per-bot voice and voice-language settings. The build is plainly circulating — but there is still no announcement or changelog entry from SpaceXAI itself, so the rumor stays unresolved.

An unannounced model named Obsidian 3 appeared in the public data behind Cognition's FrontierCode 2.0 leaderboard on its October 28 launch day, scored 46.8% at high effort against 45.5% for Claude Opus 5.5 at max, and was gone from the file within hours. Because the run used the claude-code harness, X posts quickly read it as Anthropic's long-rumored Claude Fable 5.5.

The identification is far from settled. One detailed Fable 5.5 tracker notes that the file gave Obsidian 3 the same chart colour as Meta's Muse Wonder 1.0, not the orange used for every Claude model, and a separate check of the claim notes the hidden row is not in Cognition's published table and traces to a single X post.

At max effort the two models were reportedly tied, and Obsidian 3 was said to cost several times more per task than Opus 5.5. Anthropic has still announced no Fable 5.5 — its newsroom, checked October 28, lists Haiku 5.5 as its latest model — so this stays a rumor, and a thin one, until a lab claims the name.

DeepSeek and MiniMax have won Chinese state approval for global use of their AI models, according to a post on Thursday, October 22, by Yuyuan Tantian, a social media account affiliated with state broadcaster CCTV, Reuters reported on October 23. A follow-up post on Friday said overseas users had urged other Chinese open-source labs to follow suit.

Neither DeepSeek nor MiniMax replied to Reuters' requests for comment, and no official document has been published — so the Wire is carrying this as a rumor until the labs or a regulator confirm it directly. State-media-affiliated accounts have trailed Chinese AI policy moves before, but they are not the approval itself.

The timing is the story. China proposed export controls on 23 AI technologies on October 16, covering overseas deployment of models, agents and computing clusters, while the commerce ministry said most AI technology would stay exportable, with simplified licensing for open-source exports. An approval for the country's two best-known open-weight labs would be the first clear sign of where that line is being drawn.

OpenAI is reportedly close to another mega-round of private funding instead of going straight to its IPO: up to $30 billion at a $1.25 trillion pre-money valuation, in a round led by Coatue and investors in the UAE, sources told CNBC, via TechCrunch's October 22 report. OpenAI told investors on Thursday that it wants signatures locked in by the end of next week, and the financing is being positioned as an 'opportunistic' bridge ahead of a public listing.

The number has already moved once. Bloomberg reported a month ago that OpenAI was working on raising $30 billion at a $1.4 trillion valuation, and both outlets note the terms are still being negotiated and could change. CNBC also reports the UAE funding could be coupled with a commercial deal securing more computing capacity for OpenAI from the UAE. OpenAI declined to comment.

For scale: OpenAI filed confidential IPO paperwork in June, its last raise in March valued it at $852 billion post-money, and CFO Sarah Friar has pointed employees to a 2027 IPO timeline. A close above $1 trillion would make OpenAI the most valuable private company on record and would raise the bar further for Anthropic's own debut — reports have Anthropic seeking a $1.5 to $2 trillion valuation, after raising $65 billion at $965 billion in May and also filing confidentially in June. An October 23 follow-up in The Decoder, citing the Financial Times, adds colour on why the target moved: demand was weaker than in previous rounds, with some backers experiencing 'indigestion' after heavy investments in earlier fundraises. UAE investors and Coatue are reported to be leading the round. Treat this as rumor-grade until the round actually closes: it rests on anonymous sources, and the valuation has already slipped $150 billion in a month of reporting.

TestingCatalog reported on October 20 that Muse Confidential VM, Meta's planned fully-private mode for its Muse agent, is now partially implemented in the web interface. A dedicated settings section appears to let users enable it, and the notice says conversations would run in a secure, encrypted environment that keeps data private even from Meta, with data in this mode not used to train Meta's models.

That is a step beyond the existing Muse Secure VM: Confidential VM is designed so the whole VM, including a person's data and conversations, is encrypted with a key only the user holds. Meta confirmed in September that it plans to introduce the technology before the end of 2026.

The private mode looks limited at first: voice mode, image and video generation, and wearables such as Meta AI glasses and the Muse pin may not be available, and access appears restricted to Meta AI subscribers, with upgrade prompts before users can turn it on. No release date is confirmed, so this stays a rumor until Meta ships it.

Nscale is in talks to sell computing power to Anthropic in a deal that could be worth about $45 billion, Bloomberg News reported on October 19, via Reuters. The Nvidia-backed cloud firm is seeking a second major agreement with the Claude maker, this time for another facility at its Monarch data center campus in West Virginia, running on Nvidia's next-generation Vera Rubin systems.

The talks follow an earlier Anthropic-Nscale agreement of roughly the same value announced in August, which would put the pair's combined commitments near $90 billion if the second deal lands on similar terms. Nscale and Anthropic did not respond to Reuters' requests for comment, and Reuters said it could not independently verify the report.

The timing cuts both ways for Nscale: it confidentially filed for a US listing last month with Microsoft and Anthropic as its two anchor customers, but Microsoft walked away from Nscale's Essex flagship this week after grid power slipped into the 2030s. Nothing is signed, so this stays a rumor until one of the companies confirms it.

RuntimeWire reported on October 19 that a comparison of preserved Claude web-client bundles found a new gated organization setting, 'drifting_dusk_cc_enabled', in the October 19 capture that was not present on October 14. The setting sits beside DKIM controls and is wired to an organization-update API.

The name suggests a possible way to CC Claude on email, managed through Anthropic's organization settings. RuntimeWire is careful about the bounds: the client code does not establish a customer rollout, and it does not show that Claude can join or reply to email threads.

How such a feature would relate to Claude's existing Gmail and Outlook connectors is also unknown. Until Anthropic announces anything, this stays a rumor based on reverse engineering of shipped client code, not a product launch.

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.

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.

A security researcher, Sunil Tripathy, published a disclosure on October 15 describing a flaw in ChatGPT's GitHub integration: hidden instructions in a public repository allegedly led the agent, during a routine review request, to modify a different private repository and trigger a GitHub Actions workflow.

In the researcher's test, which used accounts he controlled and a dummy secret, the workflow sent the test value to an external server. He assigns the finding a CVSS 4.0 score of 9.3; that rating is his own assessment, not a vendor classification.

Treat this as an unverified report for now. The write-ups all trace back to the single disclosure, the findings have not been independently verified, and the coverage includes no confirmation from OpenAI. The pattern it describes is indirect prompt injection: hostile instructions arriving inside material the assistant is asked to read.