← All digests
AI Developer Digest

Wed, Jun 24, 2026

19 signals that cleared the gate23 min read
The Signal — start here
June 24 is a migration deadline day. Google's Imagen API shut down today — developers still calling imagen-3-generate-001 or any imagen-* generation endpoint are returning errors right now. Compounding this, gemini-3.1-flash-image-preview and gemini-3-pro-image-preview shut down TOMORROW (June 25), so any interim migration to the preview models buys exactly one day before breaking again — migrate directly to the GA targets. Outside the deprecation story, Mistral OCR 4 shipped yesterday with bounding boxes, typed-block classification, and confidence scores at $4/1k pages with a single-container self-hosted option — the most complete structured document extraction API available today. llama.cpp b9784 delivered a substantial Qualcomm Hexagon MUL_MAT overhaul, the third Snapdragon-relevant improvement from the project in three consecutive days.
Must-reads today
1
Imagen API shutdown (TODAY) — all imagen-* generation models return errors as of June 24; migrate to gemini-3.1-flash-image or gemini-2.5-flash-image immediately; preview model successors shut down TOMORROW
2
Mistral OCR 4 — SOTA structured document extraction at $4/1k pages; bounding boxes + typed-block classification + confidence scores + 170 languages + self-hosted option; strong benchmark case for replacing managed OCR services

Breaking Changes

1
●Breaking

Google Imagen Models Shut Down — All `imagen-*` Endpoints Return Errors as of June 24

What changed
All standard Imagen 3 generation models (imagen-3-generate-001 and related imagen-3.* generation endpoints) are retired as of June 24 on both the Gemini Developer API and Vertex AI Gemini API. The client.models.generate_images() call pattern is no longer supported. Also effective today, the GenerativeModel + Imagen path is removed; the only supported image generation path is GenerativeModel.generate_content() with GenerationConfig and optional ImageConfig targeting a Gemini Image model.
TL;DR
imagen-3-generate-001 and the client.models.generate_images() API method are gone as of today; replace with gemini-3.1-flash-image (GA) or gemini-2.5-flash-image and switch to generate_content() with ImageConfig.
Developer signal
If your app calls any imagen-* model via the Gemini Developer API or Vertex AI Gemini API, it is returning errors right now — there is no grace period. The migration involves two code changes: (1) swap the model string from imagen-3-generate-001 to gemini-3.1-flash-image or gemini-2.5-flash-image (the GA "Nano Banana" models), and (2) replace ImagenModel / client.models.generate_images() with GenerativeModel / generate_content() using GenerationConfig with an optional nested ImageConfig. The Gemini Image models produce similar output quality for generation tasks. IMPORTANT: Do NOT migrate to gemini-3.1-flash-image-preview or gemini-3-pro-image-preview as an interim step — those preview models shut down TOMORROW (June 25). Migrate directly to the GA versions: gemini-3.1-flash-image and gemini-3-pro-image. A separate shutdown is coming: imagen-3.0-capability-001 (Vertex AI mask-based editing — inpainting, background masking, semantic editing) retires June 30 and has NO equivalent in Gemini 3.x Image models. If you use mask-based editing, start evaluating third-party alternatives (Stable Diffusion inpainting, FLUX Fill, etc.) now — there is currently no drop-in replacement on the Google platform. Imagen 4 models (standard/ultra/fast) have a separate August 17 shutdown date.

Affects you ifYou call any imagen-3.* model via the Gemini Developer API or Vertex AI Gemini API; or you use imagen-3.0-capability-001 for mask-based image editing on Vertex AI (shutdown June 30 with no replacement); or you deployed gemini-3.1-flash-image-preview or gemini-3-pro-image-preview as an interim migration step (those shut down tomorrow, June 25).EffortModerate (two code changes: model string + API call pattern; test image output quality on your use cases with the Gemini Image models before deploying; mask editing users face Significant effort as no equivalent API exists on Google's platform).
Google AI for Developers / Gemini API Deprecations | Date: June 24, 2026 | Link: https://ai.google.dev/gemini-api/docs/deprecationshttps://ai.google.dev/gemini-api/docs/deprecations | Migration guide: https://firebase.google.com/docs/ai-logic/imagen-models-migration

Model Releases

No new model releases in the June 23–24 scan window. Claude Tag (June 23) and OpenAI Daybreak expansion (June 22) covered in the June 23 digest. LMArena top 5 unchanged: Claude Opus 4.8 (~1510 ELO), GPT-5.5 Pro, Gemini 3.1 Pro Preview, Claude Opus 4.7, GPT-5.5.

API & SDK Changes

No new API or SDK changes in the June 23–24 scan window beyond the Imagen shutdown covered in [BREAKING] above.

  • Anthropic Platform release notes: last entry June 15, 2026.
  • OpenAI Platform changelog: last relevant API entries June 17–22 (covered in prior digests).
  • Gemini API changelog: last entry before June 24 was May 28, 2026.
  • Anthropic SDK Python: last release v0.111.0 (June 18, outside window).
  • OpenAI Python SDK: last release v2.43.0 (June 17, outside window).

Research

Nothing cleared the quality bar this period. arXiv cs.AI and cs.CL access continues to return HTTP 403 on direct list fetch (consistent with prior digests). Search-based fallback found no papers from recognized labs (DeepMind, Meta FAIR, CMU, Stanford, MIT, AI2, Mila, ETH, Oxford, Google, Microsoft, Anthropic) with both a linked code repository and measurable benchmark numbers submitted June 23–24.

Tooling

2
Medium

Mistral OCR 4: SOTA Structured Document Extraction with Bounding Boxes, Typed Block Classification, and Confidence Scores

What changed
Mistral OCR 4 adds three new structured output layers on top of text extraction: per-element bounding boxes (spatial localization), typed-block classification (titles, tables, equations, signatures, and more), and inline confidence scores at both page and word level. OCR 3 returned text; OCR 4 returns a structured document representation. The model supports 170 languages across 10 language groups (vs OCR 3's narrower coverage) and ships with a single-container self-hosted deployment option. Pricing is $4/1k pages ($2/1k with Batch API discount) — the same price tier as OCR 3.
TL;DR
Mistral OCR 4 tops OlmOCRBench at 85.20 and achieves 72% average win rate over all leading OCR and document-AI systems in blind annotator preference tests; adds bounding boxes, typed-block classification, and word-level confidence scores to text extraction, at $4/1k pages with a self-hosted option.
Developer signal
If you have an existing Mistral OCR integration, upgrade to OCR 4 — the pricing is unchanged and the additional structured output (bounding boxes, block types, confidence scores) is additive. The bounding boxes make it possible to reconstruct document layout without a separate layout analysis step, which matters for table extraction, form parsing, and document-level RAG where position context improves retrieval. For teams building document intelligence pipelines with data residency requirements, the single-container self-hosted deployment is the key new option — you can run OCR 4 on-premise or in your own cloud tenant without API round-trips. The typed-block classification (equations, tables, signatures) enables conditional post-processing: route detected table blocks to a table parsing step, route equation blocks to LaTeX rendering, route signature blocks to verification workflows. OCR 4 is an ingestion component of the Mistral Search Toolkit (open-source, composable RAG framework) — if you're already in that stack, the structured output feeds citation-ready inputs to the retrieval and evaluation pipeline. Model ID for the API has not been explicitly published in accessible sources; use mistral-ocr-latest or check the Mistral docs at docs.mistral.ai for the versioned ID. Available via Mistral API, Mistral Studio, Amazon SageMaker, and Microsoft Foundry.

Affects you ifYou use Mistral OCR 3 or any managed OCR service (AWS Textract, Google Document AI, Azure Document Intelligence) and want structured output (bounding boxes, block classification, confidence scores); or you are building document intelligence pipelines with data residency requirements where a self-hosted OCR option matters; or you process tables, equations, or signatures at scale.EffortModerate (API endpoint swap for existing Mistral OCR users; new output fields require parsing changes to consume bounding boxes and confidence scores; self-hosted deployment requires container setup).
Mistral AI | Date: June 23, 2026 | Link: https://mistral.ai/news/ocr-4/https://mistral.ai/news/ocr-4/
Notable

llama.cpp b9784: Major Hexagon Architecture Overhaul — MUL_MAT Optimization for Qualcomm Devices

What changed
PR #24954 delivers the most substantial Qualcomm Hexagon MUL_MAT optimization to date. Changes: 32×32 tiled weight repack format replaces the legacy x4x2 pattern; dynamic quantization for q8_0 and q8_1 reformatted for reduced overhead; weight tiles aligned to DMA for direct memory access; matmul kernel selection and parameter computation moved to host; kernel-params caching added to avoid redundant graph recomputation across calls; HVX (Hexagon Vector eXtensions) and HMX-specific microkernel factorization added for better parallel thread distribution; support for Hexagon architecture versions below v73 removed; OLMoE and LFM model support fixes included.
TL;DR
llama.cpp b9784 rewrites the Hexagon MUL_MAT kernel with 32×32 tiled weight repacking, DMA-aligned memory layout, and kernel-params caching — the largest single Hexagon optimization PR in recent releases, directly impacting inference throughput on all Qualcomm Snapdragon devices running llama-server.
Developer signal
Update to b9784 if you run llama.cpp on any Qualcomm Snapdragon device (Snapdragon X Elite, Snapdragon 8 Gen series phones, or other Hexagon DSP hardware). The DMA alignment and kernel-params caching in particular should reduce per-token latency on Hexagon. The removal of Hexagon <v73 support means if you are on an older Qualcomm SoC (pre-Snapdragon 888), these optimizations require b9783 or earlier. No changes to API, model compatibility (except the OLMoE/LFM fixes), or command-line flags. The OLMoE and LFM bug fixes are a bonus: if you run either of those model families on llama.cpp, b9784 resolves previous support issues. No benchmark numbers were published with this release — measure inference speed on your target hardware before and after if you need quantified improvement data.

Affects you ifYou run llama.cpp on Qualcomm Snapdragon hardware (Snapdragon X Elite laptops, Snapdragon-based Android devices, Qualcomm AI PC hardware) and use quantized model inference via llama-server or the CLI; or you run OLMoE or LFM models on any llama.cpp build.EffortQuick (binary update; no model or config changes required; Hexagon <v73 users should stay on b9783 or earlier).

Benchmarks & Leaderboards

No leaderboard movements or new SOTA entries on June 23–24.

  • LMArena: Top 5 unchanged (Claude Opus 4.8, GPT-5.5 Pro, Gemini 3.1 Pro Preview, Claude Opus 4.7, GPT-5.5). No new model additions June 23–24 confirmed.
  • SWE-bench Verified: Unchanged. Claude Opus 4.8 at 88.6%.
  • Kimi K2.7 Code: Still no independent third-party SWE-bench, LiveCodeBench, or GPQA results. Vendor-reported proprietary benchmarks only. See Worth Watching.

Technical Discussions

Nothing cleared the quality bar this period. No Hacker News threads with score >200 for AI developer topics identified in the June 23–24 window. No r/MachineLearning or r/LocalLlama threads with sufficient technical depth and recency confirmed.

Quick Hits

  • llama.cpp b9781 (June 24, 15:01 UTC) — Vulkan graph submission batching: reduces graph submission batch sizes to avoid GPU command-buffer timeout errors on systems with strict GPU timeout constraints. Relevant if you use llama.cpp with the Vulkan backend (AMD, Intel, or non-NVIDIA GPUs on Linux) and have seen GPU timeout failures under load. [https://github.com/ggml-org/llama.cpp/releases/tag/b9781]
  • llama.cpp b9782 (June 24, 16:44 UTC) — Removes unused json-partial from the common codebase. Maintenance only; no behavior change. [https://github.com/ggml-org/llama.cpp/releases/tag/b9782]
  • Modal Auto Endpoints (June 23, 2026) — Single-command production LLM inference deployment: modal endpoint create --name agent --model <model-id> (e.g., zai-org/GLM-5.2-FP8). Wraps Modal Servers (low-latency routing layer, now GA from beta) with autoscaling inference into a one-command deploy path. Relevant if you currently write custom Modal Function boilerplate for LLM serving. [https://modal.com/blog/introducing-auto-endpoints]

Worth Watching (Announced, Not Yet Shipped)

15

⚠️⚠️⚠️ Gemini Image Preview Model Shutdown — **TOMORROW June 25 (1 day)**

(Countdown updated — was 2 days)

gemini-3.1-flash-image-preview and gemini-3-pro-image-preview shut down June 25. Migrate to GA versions: gemini-3.1-flash-image and gemini-3-pro-image. Do NOT use these preview models as an interim migration target from today's Imagen shutdown — they die tomorrow.

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

(Countdown updated — was 4 days)

GPT-4.5 removed from ChatGPT product surface June 27. API route retirement unconfirmed; audit any gpt-4.5 model identifiers in product or prompt code.

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

⚠️⚠️⚠️ imagen-3.0-capability-001 Retirement — **June 30 (6 days) — NO REPLACEMENT**

(New entry — just confirmed)

imagen-3.0-capability-001 (Vertex AI mask-based editing: inpainting, background masking, semantic editing) retires June 30 with no replacement in the Gemini 3.x image stack. No migration path announced. Evaluate third-party alternatives (FLUX Fill, Stable Diffusion inpainting) now if you use mask-based editing workflows.

⚠️⚠️⚠️ Video Generation Models Shutdown — **June 30 (6 days)**

(New entry — just confirmed)

Video generation models shutting down June 30. Recommended migration: Veo 3.1 preview model IDs. Check the deprecations page for specific model IDs affected.

⚠️⚠️ Kimi K2.7 Code Third-Party Benchmarks — **Still Pending (Expected June 23–27)**

(Status: still no independent results — extended window)

Weights released June 12, Arena entry June 17. As of June 24, no SWE-bench Verified, SWE-bench Pro, LiveCodeBench, or GPQA results from independent evaluators. Only vendor-reported proprietary benchmarks exist. Watch swebench.com and livecodebench.github.io.

⚠️⚠️ Gemini Code Assist for GitHub Full Shutdown — **~Mid-July (~21 days)**

(Countdown updated — was ~22 days)

New organizational installs blocked June 18. Full request serving ends approximately mid-July. Organizations using Gemini Code Assist for GitHub need an alternative.

⚠️ Grok V9-Medium — **API Release Still Pending**

(Status unchanged)

xAI deployed Grok V9-Medium to Tesla fleet and X users (1.5T parameters, 32B active). No API model ID, pricing, or public benchmarks as of June 24.

⚠️ Claude Fable 5 / Mythos 5 Reinstatement — **No Timeline Announced**

(Status unchanged)

Both models remain suspended under the US export-control directive issued June 12. Migrate to claude-opus-4-8 for agentic workloads.

⚠️ Gemini 3.5 Pro — **GA Still Pending (Limited Vertex Enterprise Preview)**

(Status unchanged)

Expected: 2M token context, Deep Think reasoning mode. No GA date confirmed.

⚠️ Imagen 4 Model Shutdown — **August 17 (54 days)**

(New entry — confirmed)

Imagen 4 standard, ultra, and fast endpoints deprecated with August 17, 2026 shutdown date. Separate from today's Imagen 3 shutdown.

Apple iOS 27 / macOS Golden Gate / Core AI GA — **Fall 2026 (September)**

(Status unchanged)

Includes Siri Extensions API, Core AI (replaces Core ML), Foundation Models multi-provider support (call Claude/Gemini via same Swift API as on-device model).

Apple Developer / WWDC 2026 | Link: https://developer.apple.com/ios/

⚠️ OpenAI Reusable Prompts / Evals Platform / Agent Builder Shutdown — **November 30 (159 days)**

(Countdown updated — was 160 days)

Export eval configs before October 31. Migrate Agent Builder to Agents SDK. Move prompt content from v1/prompts to application code.

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