← All digests
AI Developer Digest

Sun, Jun 28, 2026

18 signals that cleared the gate20 min read
The Signal — start here
June 27-28 was quiet after the GPT-5.6 splash on June 26 — no new model releases, no API breaking changes from the major labs, and no confirmed leaderboard movements. The one item developers should act on immediately is CVE-2026-12957: Amazon Q Developer's extension (VS Code, JetBrains, Eclipse, Visual Studio) auto-executed MCP server configs from .amazonq/mcp.json files in any opened workspace, inheriting the developer's full environment including AWS credentials. Fix is Language Servers for AWS 1.69.0, released ahead of the June 26 public disclosure. This item was not in the June 26 digest and requires immediate action. Beyond the security fix, llama.cpp continued its rapid cadence with OpenCL flash attention reworked to support f16/f32 prefill and quantized formats, DFlash v2 for hybrid-attention models, and MiniCPM5 tool call support added.
Must-reads today
1
CVE-2026-12957 Amazon Q Developer — if you use Amazon Q in any IDE with MCP enabled, update Language Servers for AWS to 1.69.0 now; a .amazonq/mcp.json in a malicious repo could run arbitrary code and steal your AWS credentials on git clone
2
llama.cpp b9828 OpenCL flash attention — meaningful for anyone on Intel/AMD/mobile GPU via the OpenCL backend; f16/f32 kernel rework + quantized (q4_0/q8_0) prefill support closes the gap with CUDA and Metal backends

Breaking Changes

1
●Breaking

CVE-2026-12957: Amazon Q Developer Auto-Executes MCP Configs from Untrusted Repos — AWS Credentials at Risk

What changed
Amazon Q Developer's Language Servers for AWS runtime (powering the Amazon Q extension across VS Code, JetBrains, Eclipse, and Visual Studio) automatically loaded and executed MCP server configurations from .amazonq/mcp.json in any opened workspace — with no user prompt, no workspace trust verification, and no sandboxing. MCP servers are local processes that inherit the developer's full environment: AWS credentials, cloud CLI tokens, API secrets, SSH agent sockets. A second flaw, CVE-2026-12958, allowed arbitrary file writes outside the workspace boundary via a missing symlink check. The fix adds workspace trust verification before executing MCP configs; fix version is Language Servers for AWS 1.69.0 (initial patch 1.65.0 — AWS bulletin directs to 1.69.0).
TL;DR
CVE-2026-12957 (CVSS 8.5) in Amazon Q Developer allowed a malicious .amazonq/mcp.json to auto-execute MCP servers and exfiltrate cloud credentials; patch to Language Servers for AWS 1.69.0 immediately.
Developer signal
Update Language Servers for AWS to 1.69.0 or later in VS Code (Extensions > AWS Toolkit / Amazon Q), JetBrains, Eclipse, or Visual Studio now. All four IDE plugins bundle the Language Servers runtime and all were exposed. After updating, Amazon Q will prompt for workspace trust confirmation before loading any MCP configuration from an unverified workspace. Until updated, do not open repositories from untrusted sources with Amazon Q active. If you opened untrusted repos with an unpatched version: audit AWS CloudTrail for unexpected API calls from your developer machine, rotate credentials that were present in your environment during affected sessions, and check ~/.aws/credentials for unexpected access. The attack requires only git clone + opening the workspace in an affected IDE — no further user interaction. No public exploits confirmed (CISA ADP: none known as of June 26), but the attack surface is trivially exploitable in code review workflows where developers routinely open external PRs. Discovery and coordinated disclosure: Wiz Research, reported April 20; Amazon fix deployed May 12; public disclosure June 26 under Amazon Security Bulletin 2026-047-AWS.

Affects you ifYou use the Amazon Q Developer extension in VS Code, JetBrains, Eclipse, or Visual Studio with MCP configurations enabled; you regularly clone or open external repositories (PRs, reviews, evaluation); your development environment carries AWS credentials or cloud CLI tokens in environment variables or ~/.aws/credentials.EffortQuick (extension update via IDE extension manager; no code changes required — update Language Servers for AWS to 1.69.0).
Wiz Research | Date: June 26, 2026 | Link: https://www.wiz.io/blog/amazon-q-vulnerabilityhttps://www.wiz.io/blog/amazon-q-vulnerability | Amazon Security Bulletin 2026-047-AWS

Model Releases

No model releases in the June 27-28 scan window. GPT-5.6 Sol/Terra/Luna remains in limited preview (~20 partner organizations); no new LMArena or SWE-bench submissions confirmed in window.

API & SDK Changes

No API or SDK changes from Anthropic, OpenAI, Google, Mistral, or Meta in the June 27-28 scan window.

Research

Nothing cleared the quality bar this period. arXiv cs.AI and cs.CL new submissions for June 27-28 returned no papers from recognized labs with both a linked code repository and measurable benchmark numbers that were newly submitted in this window.

Tooling

3
Notable

llama.cpp b9828: OpenCL Flash Attention Reworked — f16/f32 + Quantized (q4_0/q8_0) Prefill Support

What changed
The OpenCL backend's flash attention kernels were fully reworked to support f16 and f32 data types with prefill prepass kernels added, alongside q4_0 and q8_0 quantization in the attention path. Prior to b9828, the OpenCL flash attention implementation had more limited format coverage than the CUDA and Metal backends. This continues the multi-backend hardware coverage focus visible across June 2026 llama.cpp builds (OpenVINO self-contained packaging in b9817, Intel Xe-LPG Plus cooperative matrix in b9813, CUDA Memcpy2DAsync fast path in b9827).
TL;DR
llama.cpp b9828 ships reworked OpenCL flash attention with f16/f32 and quantized (q4_0/q8_0) prefill on June 27, 2026, narrowing the OpenCL backend's gap with CUDA and Metal on Intel, AMD, and mobile GPU targets.
Developer signal
If you run llama.cpp inference via the OpenCL backend — common on Intel integrated and Arc discrete GPUs, AMD GPUs without ROCm driver support, and Android/ARM GPU deployments — update to b9828 or later for improved attention kernel coverage. No config changes required; the kernel improvements are backend-transparent. Pull the updated binary for your platform or rebuild from source. On AMD hardware without ROCm, the OpenCL path is now more complete for quantized attention, which may reduce VRAM pressure in the prefill phase. Track your per-token throughput before and after the update on any affected setup.
Affects you ifYou run llama.cpp with --gpu-layers on Intel or AMD GPUs via the OpenCL backend; you deploy llama.cpp on platforms without CUDA or Metal (Intel Arc, AMD without ROCm, Android GPU inference).EffortQuick (update binary or rebuild from source; no config changes).
Notable

llama.cpp b9831: DFlash v2 + Per-Layer Sliding Window Attention Support

What changed
DFlash v2 specification integrated, with sliding window attention configurable per layer type. Previously, sliding window attention was applied uniformly across layers; b9831 enables hybrid-attention model architectures where some layers use full attention and others use sliding window attention. This is the attention pattern used in Mistral models, newer Mamba2 variants, and other architectures combining global and local attention heads.
TL;DR
llama.cpp b9831 adds DFlash v2 support with per-layer-type sliding window attention, enabling correct inference for hybrid-attention-architecture models including Mistral and custom Mamba2 variants.
Developer signal
If you run Mistral models, Mamba2 variants, or any open model with a hybrid attention architecture (full + sliding window layers) via llama.cpp, b9831 ensures correct attention mask computation per layer. No config changes required — layer-type dispatch is handled from model metadata. Update to b9831+ if you observe unexpected output quality or attention artifacts on any hybrid-attention model. This also complements b9804 (June 26, Mamba2 variable expansion factors) — running Mamba2 variants benefits from both updates.
Affects you ifYou run Mistral models, Mamba2 variants, or other hybrid-attention-architecture models in llama.cpp; you are evaluating newer open-source models with non-standard attention configurations.EffortQuick (update binary or rebuild; no config changes).
Notable

llama.cpp b9833: MiniCPM5 Tool Call Parser Added — XML-Based Function Calling Support

What changed
Added a dedicated tool call parser for MiniCPM5 models using an XML-based format, with grammar refactoring and fixed streaming placeholders. Before b9833, MiniCPM5 tool calls in llama.cpp would fall back to a generic parser that does not correctly handle MiniCPM5's XML tool call schema, producing malformed or missing tool call outputs in agentic workflows.
TL;DR
llama.cpp b9833 adds native MiniCPM5 tool call parsing (XML format), enabling correct function calling and agentic workflows with MiniCPM5 models running locally through llama.cpp's server API.
Developer signal
If you are running MiniCPM5 locally for agentic tasks or function calling via llama.cpp's /v1/chat/completions API with tools parameter, b9833 is the minimum version for tool calls to work correctly. Update the binary and test your tool-calling workflow against the new parser. If you previously worked around MiniCPM5 tool call issues by post-processing raw completions, the dedicated parser should eliminate that need.

Affects you ifYou run MiniCPM5 models locally via llama.cpp with tool use or function calling; you are benchmarking MiniCPM5 agentic capabilities on local hardware.EffortQuick (update binary or rebuild).

Benchmarks & Leaderboards

No leaderboard movements or new SOTA entries confirmed in the June 27-28 scan window.

  • LMArena Overall: Top 5 unchanged from June 26 — Claude Opus 4.8 (~1510 ELO), GPT-5.5 Pro, Gemini 3.1 Pro Preview, Claude Opus 4.7, GPT-5.5. GPT-5.6 not yet submitted (limited to ~20 preview partners; Arena requires broader access).
  • SWE-bench Verified: No changes confirmed. Last known: Claude Mythos 5 at 95.5%, Claude Fable 5 at 95.0%, Claude Opus 4.8 at 88.6%.
  • SWE-bench Pro: Claude Opus 4.8 at 69.2%; no changes in window.

Technical Discussions

Nothing cleared the quality bar this period. No Hacker News threads with score >200 for AI developer topics confirmed for June 27-28. Simon Willison's weblog shows no entries dated June 27-28. No r/MachineLearning or r/LocalLlama threads with confirmed June 27-28 recency and sufficient technical depth surfaced.

Quick Hits

  • GPT-4.5 ChatGPT retirement — HAPPENED June 27 — GPT-4.5 was removed from ChatGPT and custom GPTs as scheduled; existing conversations migrate to GPT-5.5. Note: the GPT-4.5 API endpoint was already deprecated in July 2025 — no API-level action required now.
  • llama.cpp b9827 (June 27, 12:49 UTC) — CUDA cudaMemcpy2DAsync 2D pitched block transfer fast path for strided tensor copies; optimizes non-contiguous data layout operations in multi-GPU and large-batch setups. [https://github.com/ggml-org/llama.cpp/releases/tag/b9827]
  • llama.cpp b9830 (June 28, 11:03 UTC) — --offline flag exposed for llama download (verify local model cache without network access); also fixes a use-after-free bug in URL task callbacks. [https://github.com/ggml-org/llama.cpp/releases/tag/b9830]

Worth Watching (Announced, Not Yet Shipped)

13

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

(Countdown updated — was 4 days)

imagen-3.0-capability-001 (Vertex AI mask-based editing: inpainting, background masking, semantic editing) retires June 30 with no replacement. Evaluate third-party alternatives (FLUX Fill, Stable Diffusion inpainting) now if you use mask-based editing workflows — these are self-hosted only, no managed API replacement exists.

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

(Countdown updated — was 4 days)

Video generation models shutting down June 30. Recommended migration: Veo 3.1 preview model IDs.

⚠️⚠️ GPT-5.6 Sol/Terra/Luna General Availability — **Coming Weeks (unconfirmed)**

(Status unchanged — limited to ~20 partner organizations)

No GA date set. Watch the OpenAI platform changelog. When GA lands, cache write pricing (1.25x write cost) and explicit cache breakpoints go live — audit caching architecture before adopting.

⚠️⚠️ GPT-5.6 Sol on Cerebras — **July 2026 (~2 days)**

(Countdown updated — was ~5 days)

GPT-5.6 Sol at up to 750 tokens/second on Cerebras hardware. Targeted early July 2026; no specific date given.

⚠️⚠️ Kimi K2.7 Code Third-Party Benchmarks — **Still Pending**

(Status unchanged — no independent results as of June 28 scan)

Weights released June 12; Arena entry June 17. No SWE-bench Verified, LiveCodeBench, or GPQA results from independent evaluators as of June 28.

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

(Countdown updated — was ~18 days)

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

⚠️ Claude Mythos 5 — **Still Suspended**

(Status unchanged)

Remains suspended under US export-control directive. Claude Fable 5 reinstated June 18. Mythos 5 reinstatement timeline not announced. Migrate agentic workloads to claude-opus-4-8.

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

(Countdown updated — was 52 days)

Imagen 4 standard, ultra, and fast endpoints deprecated with August 17, 2026 shutdown date.

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 (155 days)**

(Countdown updated — was 157 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.