OpenAI quietly retires GPT-5.2, defaults the install base to GPT-5.5, and a 1.5M-context GPT-5.6 "Kindle-Alpha" leaks the same weekend
All three GPT-5.2 variants — Instant, Thinking and Pro — were taken offline Friday with no announcement. Existing ChatGPT conversations now route silently to the corresponding GPT-5.5 tier. A checkpoint labelled GPT-5.6 "kindle-alpha" — internally codenamed iris-alpha — surfaced through Codex test paths over the same 48 hours with reports of a 1.5 million token context, medium reasoning effort by default, and sharply cleaner SVG output. OpenAI has issued no system card, no pricing, no benchmark suite and no safety evaluation, leaving the GPT-5.5 family as the only API-supported endpoint for the install base after this weekend.
TechTimes · 2026-06-13 · Source ↗ ·
OpenAI quietly retires GPT-5.2, defaults the install base to GPT-5.5, and a 1.5M-context GPT-5.6 "Kindle-Alpha" leaks the same weekend
All three GPT-5.2 variants — Instant, Thinking and Pro — were taken offline Friday with no announcement. Existing ChatGPT conversations now route silently to the corresponding GPT-5.5 tier. A checkpoint labelled GPT-5.6 "kindle-alpha" — internally codenamed iris-alpha — surfaced through Codex test paths over the same 48 hours with reports of a 1.5 million token context, medium reasoning effort by default, and sharply cleaner SVG output. OpenAI has issued no system card, no pricing, no benchmark suite and no safety evaluation, leaving the GPT-5.5 family as the only API-supported endpoint for the install base after this weekend.
TechTimes · 2026-06-13 · Source ↗ ·
OpenAI shut down the entire GPT-5.2 family on Friday June 12 without an announcement. The three variants — GPT-5.2 Instant, GPT-5.2 Thinking and GPT-5.2 Pro — were pulled from ChatGPT and the API in the same window. Existing conversations were silently re-pointed to the corresponding GPT-5.5 endpoint, so a paid user who returned to a 5.2 Pro session on Saturday found it continuing under GPT-5.5 Pro with no banner, no inbox notification and no migration warning in the developer console. TechTimes published the most complete account of the deprecation late on Saturday evening Eastern, and the same story carries the first detailed write-up of the GPT-5.6 "Kindle-Alpha" checkpoint that leaked through Codex testing channels in the same weekend.
The mechanical effect of the swap is that GPT-5.5 is now the floor of OpenAI's customer-facing model ladder. The article frames the transition carefully: GPT-5.5 is more capable on most public benchmarks than GPT-5.2 across all three tiers, but it is not a byte-for-byte replacement. Tone, verbosity, formatting habits, refusal behavior and edge-case handling have all shifted measurably. Teams that pinned prompts against GPT-5.2 idiosyncrasies — many production agents do — will need to re-evaluate. The TechTimes piece is unusually pointed about that: it tells developers to verify that no production code references GPT-5.2 strings, re-test prompts against GPT-5.5, pin explicit model versions in API calls, and defer GPT-5.6 planning until OpenAI publishes an official card.
"Existing ChatGPT conversations that previously used GPT-5.2 have been automatically migrated to the corresponding GPT-5.5 variants — but GPT-5.5 is not a byte-for-byte replacement for GPT-5.2."— TechTimes, June 13, 2026
What the 5.6 leak actually contains
A separate Windows Forum thread broke the GPT-5.6 leak last weekend and TechTimes consolidates the trail. An internal checkpoint labelled "kindle-alpha" surfaced through developer testing channels on June 3, with the leak tracing through Codex evaluation paths that were not gated correctly. Community reverse-engineering tied the checkpoint to earlier codenames ember-alpha and beacon-alpha, and to an internal codename iris-alpha that has appeared in OpenAI shipping artifacts since April. Reports converge on three claims: stronger reasoning and coding than GPT-5.5 across head-to-head spot tests; visibly cleaner SVG and frontend code generation from minimal prompts; and a 1.5 million token context window, roughly 43 percent larger than GPT-5.5's 1.05 million.
OpenAI has neither confirmed nor denied the leak. There is no system card, no public API endpoint, no posted pricing and no third-party benchmark suite that can be compared cleanly against GPT-5.5 or Anthropic Claude Fable 5. The model card for GPT-5.6 does not exist on OpenAI's documentation site, and any code that hardcodes "gpt-5.6" today will fail. The article underscores how unusual it is for an unreleased OpenAI checkpoint to be reasoned about in detail in public, and credits the depth of the leaked behavior — extended outputs in user sessions, working tool-use patterns, a usable assistant identity prompt — as the reason the community treats the artifact as plausibly real rather than spoofed.
"The model is reportedly configured with medium reasoning effort, indicating a balance between response quality, speed, and computational efficiency."— TechTimes summary of community reverse-engineering of the Kindle-Alpha checkpoint
Why the timing matters
The GPT-5.2 cut came in the same weekend Anthropic shipped Claude Code's /fork command and a refreshed CLI, the same weekend The Information published a long-form report on Anthropic's partner conflicts, and the same weekend SpaceX's $2.1 trillion debut absorbed every front page in financial media. OpenAI's silent removal of an entire model family on Friday — with no blog, no email, no console banner — is the kind of decision that a year ago would have come paired with a Greg Brockman tweet and a Sam Altman quote. The June 12 cut shipped with none of that. The most charitable read is that GPT-5.6 is close enough to release that OpenAI is clearing the model menu in advance. The less charitable read is that the company is running quieter on product communications during the confidential S-1 period it began on June 8.
For builders, the operational takeaway is sharp. GPT-5.5 is now the working floor. Any application that depended on GPT-5.2-specific behavior is broken or drifting today. The 5.6 leak is real enough to plan around, but specific numbers in it should be treated as unconfirmed until OpenAI ships a system card. The TechTimes piece recommends pinning explicit model versions in production API calls — a discipline OpenAI's own model deprecation policy has now made unavoidable.