← All digests
AI Developer Digest

Sun, Jun 7, 2026

16 signals that cleared the gate17 min read
The Signal — start here
A genuinely light 24-hour window. One urgent action item dominates everything else: the Gemini Interactions API opt-out header (Api-Revision: 2026-05-07) stops being accepted tomorrow at the start of June 8 — developers who haven't migrated from response.outputs to response.steps have hours, not days. Beyond that one must-act item, the one new technical development worth noting is llama.cpp b9549 landing Gemma4 Multi-Token Prediction in the official upstream repo — community testing shows ~40% throughput gain on consumer hardware with no quality loss. The rest of the period is bug fixes and minor SDK patches across the usual repos.
Must-reads today
1
Gemini Interactions API — LAST DAY before June 8 removal — if your code reads response.outputs or sends Api-Revision: 2026-05-07, it breaks tomorrow; migrate to response.steps now
2
llama.cpp b9549: Gemma4 MTP — 40% throughput gain (97 → 138 tokens/s on M5 Max) for local Gemma4 inference, no quality tradeoff

Breaking Changes

1
●Breaking

Gemini Interactions API — Legacy Schema Removal June 8, Less Than 24 Hours

What changed
The Api-Revision: 2026-05-07 opt-out header that preserved the legacy response.outputs schema stops being accepted on June 8. No grandfathering, no extended opt-out. After today, all Interactions API traffic uses only the new response.steps schema — unconditionally.
TL;DR
The Gemini Interactions API legacy response.outputs schema is removed June 8 (fewer than 24 hours); any code sending Api-Revision: 2026-05-07 or reading response.outputs stops working at the start of June 8.
Developer signal
You have today. Three things to check right now: (1) Search your codebase for response.outputs, Api-Revision: 2026-05-07, and response_mime_type. Each of these either breaks or stops working June 8. Replace response.outputs with response.steps — the steps array provides a structured timeline of each interaction turn with polymorphic entry types. (2) If you use the Python SDK (google-generativeai ≥2.0.0) or JavaScript SDK (@google/generative-ai ≥2.0.0), the SDK already automatically uses the new schema — you only need to update how your application code reads the response structure. (3) response_mime_type is gone; use the new response_format polymorphic field instead. Note: any Gemini features shipped after May 7 — including new Gemini 3.5 Flash capabilities — are only available in the new schema. Staying on the opt-out was already costing you new capabilities. Full migration guide with before/after code examples at the primary source link.

Affects you ifYou call the Gemini Interactions API directly or via SDK and your code accesses response.outputs, sends the Api-Revision: 2026-05-07 header, or references response_mime_typeEffortModerate (response-reading code must be updated; if using a current SDK version, the SDK transport layer is already migrated — only application code needs changing)

Model Releases

No new model releases in this 24h period.

API & SDK Changes

No new API or SDK changes requiring full entries in this 24h period beyond the Gemini breaking change above. See Quick Hits for anthropic-sdk-python v0.107.1 Foundry bug fix.

Research

Nothing cleared the quality bar in this 24h period. No new arXiv papers from recognized labs with measurable benchmark numbers and associated code found in the June 6–7 window.

Tooling

1
Notable

llama.cpp b9549: Gemma4 Multi-Token Prediction Lands in Official Upstream

What changed
PR #23398 merges Gemma4 MTP (Multi-Token Prediction) support into the official llama.cpp repo. Previously, Gemma4 MTP was only available in the ik_llama.cpp performance fork (PR #1744, merged May 10, 2026, with verified 2.6–2.98x lossless speedup); b9549 brings it to the main project used by most downstream integrations.
TL;DR
llama.cpp b9549 adds official Gemma4 Multi-Token Prediction support, enabling community-verified ~40% throughput gains (97 → 138 tokens/s on MacBook Pro M5 Max) with no measurable quality degradation.
Developer signal
If you're running Gemma4 locally via llama.cpp, update to b9549 and enable MTP to unlock the throughput improvement without changing your model. To enable: add --draft-model <gemma4-mtp-draft-gguf> to your llama-cli or llama-server invocation. The draft GGUF is generated from the Gemma4AssistantForCausalLM model class via the standard convert_hf_to_gguf.py conversion path. The 40% figure comes from community benchmarks on Apple Silicon (M5 Max); CUDA users should expect comparable or better gains since MTP overhead is typically lower on GPU. Before this build, using Gemma4 MTP required building from the ik_llama.cpp fork or maintaining a custom build — b9549 removes that barrier and makes MTP a standard option in any llama.cpp distribution. The ik_llama.cpp fork results (2.6–2.98x at larger batch sizes) are the upper bound; 40% is the conservative single-stream figure. Check the PR for updated configuration examples.

Affects you ifYou run Gemma4 models locally using llama.cpp and care about inference throughput on consumer or prosumer hardware (Apple Silicon, CUDA, or CPU)EffortQuick (update to b9549, generate or download a Gemma4 MTP draft GGUF, add one CLI flag — no architecture or code changes required)

Benchmarks & Leaderboards

No new leaderboard movements for June 6–7. The LMArena text leaderboard top cluster and SWE-bench Verified rankings are unchanged from the prior digest. Last significant leaderboard entry was June 5 (mistral-medium-3.5 added to Code Arena WebDev leaderboard).

Technical Discussions

Nothing cleared the quality bar this period. No HN threads with score >200 and concrete technical depth found for June 6–7. No qualifying posts from Nathan Lambert (last: June 1), Eugene Yan, or Sebastian Raschka in the scan window.

Quick Hits

Worth Watching (Announced, Not Yet Shipped)

13

⚠️⚠️ Windows Local AI Runtime — **KB5039239 June 9 (2 days)**

(Countdown updated)

Windows Update KB5039239 delivers the expanded on-device AI stack (Aion 1.0 runtime, CPU/GPU/NPU support) on June 9. Required for production use of Aion 1.0 Instruct and Aion 1.0 Plan on end-user devices. Aion 1.0 open weights land on Hugging Face in July.

⚠️⚠️⚠️ Claude Sonnet 4 + Opus 4 — Retirement **June 15 (8 days)**

(Countdown updated)

claude-sonnet-4-20250514 and claude-opus-4-20250514 return errors June 15. Migrate to claude-sonnet-4-6-20260217 and claude-opus-4-8 respectively. Review the Opus 4.8 migration guide before upgrading — adaptive thinking replaces budget_tokens; setting temperature, top_p, or top_k to non-default values returns a 400 error.

⚠️⚠️ Gemini API Unrestricted Key Deadline — **June 19 (12 days)**

(Countdown updated)

All unrestricted Gemini API keys blocked June 19. Restrict via AI Studio → API Keys → "Restrict to Gemini API." Takes 2 minutes; no code changes required.

Google AI for Developers | Link: https://ai.google.dev/gemini-api/docs/api-key

⚠️ Gemini Image Models Shutdown — **June 25 (18 days)**

(Countdown updated)

gemini-3.1-flash-image-preview and gemini-3-pro-image-preview shutting down June 25, 2026. Migrate to stable image model equivalents before the shutdown date.

⚠️ GPT-4.5 Retirement from ChatGPT — **June 27 (20 days)**

(Countdown updated)

GPT-4.5 being retired from the ChatGPT product surface on June 27; direct API route retirement unconfirmed. Audit gpt-4.5 model identifiers in code.

OpenAI Platform Changelog | Link: https://platform.openai.com/docs/changelog

⚠️ Claude Opus 4.1 Retirement — **August 5 (59 days)**

(Countdown updated)

claude-opus-4-1-20250805 retires August 5. Migrate to claude-opus-4-8. Significant migration effort if coming from a pre-4.7 model — see June 6, 2026 digest for the full migration checklist including breaking changes around adaptive thinking, sampling parameters, and tokenizer differences.

Claude Mythos — Public Release "Once Stronger Safeguards Ready"

(Carried — status unchanged)

No timeline given. Currently: no public API, no claude.ai access at any tier. Leads SWE-bench Verified at 93.9% (internal benchmark as of June 2, 2026).

Gemini 3.5 Pro — Expected July 2026

(Carried — no official date)

Sundar Pichai stated "give us until next month" at Google I/O 2026 (May 19). No official announcement, pricing, model ID, or benchmark numbers.

Filtered from 30+ primary sources against a published quality rubric. No press releases, no fluff — only what changes what you build.