← All digests
AI Developer Digest

Fri, Jun 19, 2026

17 signals that cleared the gate21 min read
The Signal — start here
The June 18-19 window is quiet on model releases — Anthropic, OpenAI, Google, Meta, and Mistral posted nothing new in this 24-hour window. The action is in developer tooling: OpenAI Codex lands Record & Replay, the first demo-based skill recording feature in a major AI coding tool; AWS closes out its Summit with Strands Agents gaining chaos testing, red teaming, and sub-millisecond sandbox execution for production hardening. The common thread across both announcements is the same: AI dev tooling is maturing from "smart completion" toward "reliable production workflow." A light period on model releases — only 3 main items — but both MEDIUM entries represent a genuine shift in what AI coding tools are trying to be, not incremental updates.
Must-reads today
1
OpenAI Codex Record & Replay — demo-to-skill recording on macOS is a new capability class; record once, replay on demand, share with the team
2
AWS Strands Evals v1.0 — first production-ready chaos testing + adversarial red teaming framework purpose-built for agents; pairs with the new sub-ms Strands Shell sandbox for CI-safe pre-deployment testing

Breaking Changes

No breaking changes from major labs or API surfaces in the June 18-19 scan window. See API & SDK Changes for Groq model ID deprecations (announced June 17, first covered in this digest) that require code migration for free/developer-tier users before those model IDs are removed.

Model Releases

No new model releases in the June 18-19 scan window. See Worth Watching for Kimi K2.7 Code third-party benchmark timing (~June 22), Grok V9-Medium pending API release, and the ongoing Gemini 3.5 Pro GA timeline.

API & SDK Changes

1
Notable

Groq Deprecates Four High-Traffic Models for Free/Developer Tier — Migrate to GPT-OSS or Qwen 3.6-27B

What changed
Groq deprecated four models for free and developer-tier users: llama-3.1-8b-instant, llama-3.3-70b-versatile, qwen/qwen3-32b, and meta-llama/llama-4-scout-17b-16e-instruct — among the most commonly used free-tier model IDs on GroqCloud.
TL;DR
Four high-traffic Groq model IDs deprecated on June 17; recommended replacements are openai/gpt-oss-20b ($0.10/M input) for lightweight workloads and openai/gpt-oss-120b ($0.15/M input) or qwen/qwen3.6-27b for 70B-class tasks.
Developer signal
If you're using any of these four model IDs in code pointed at GroqCloud's free or developer tier, update your model strings now — no confirmed removal date was available at time of writing, treat this as an immediate migration priority. Groq's recommended replacements are OpenAI's open-weight MoE models (Apache 2.0, released August 2025): openai/gpt-oss-20b for the 8B-class use case and openai/gpt-oss-120b for the 70B-class slot — note that gpt-oss-120b uses only ~5.1B active parameters per forward pass (MoE architecture), making it extremely fast on Groq's LPU hardware despite the 120B total parameter count. qwen/qwen3.6-27b is the alternative migration path for Qwen workloads. Enterprise customers with a committed-spend contract are not affected. The pattern of replacing Llama-family defaults with OpenAI open-weights is notable (see Horizon for analysis).

Affects you ifYou are calling GroqCloud's API with any of these model IDs on a free or developer-tier account: llama-3.1-8b-instant, llama-3.3-70b-versatile, qwen/qwen3-32b, or meta-llama/llama-4-scout-17b-16e-instruct.EffortQuick (update the model ID string in your code; no other changes required).

Research

Nothing cleared the quality bar in the June 18-19 window. arXiv cs.AI and cs.CL list pages returned HTTP 403 on direct fetches. Search results surfaced no papers from recognized labs (DeepMind, Meta FAIR, CMU, Stanford, MIT, AI2, Mila, ETH, Oxford, Google, Microsoft, Anthropic) with linked code and measurable benchmark numbers published June 18-19. HuggingFace Daily Papers also returned 403. See Horizon for a continuing note on arXiv scanning gaps.

Tooling

3
Medium

OpenAI Codex Record & Replay — Demo-Based Skill Recording Lands on macOS

What changed
Codex gains a macOS-native Record & Replay capability: users demonstrate a workflow once on their Mac, Codex captures the full sequence and converts it into a reusable "skill" that can be triggered repeatedly without re-demonstration, and shared across a team.
TL;DR
OpenAI Codex now lets you record a workflow on macOS and replay it as an automated, shareable skill — the first demo-to-skill recording capability shipped by a major AI coding tool, alongside Browser Use improvements and bulk automation run history actions.
Developer signal
Record & Replay is meaningfully different from Codex's existing agentic coding: instead of prompting the model to figure out a task from scratch each time, you demonstrate it once (filing expenses, publishing a release, booking a resource) and Codex stores that demonstrated path as a reusable skill. The critical open question is how robust the recording is to UI changes — traditional RPA tools (UiPath, Automation Anywhere) record exact coordinates and break when the UI shifts; if Codex uses model understanding of intent to make skills more resilient, this is a fundamentally different capability. Skills are shareable: one employee's recording becomes the team's automation, reducing drift between "what the agent does" and "what a human actually does." The June 18 update also includes: bulk actions in automation run history, new deep links for SSH connection management, and Browser Use improvements where visible-tab routing and annotations now persist when a draft browser session moves to server-side execution. Availability caveats: macOS only; explicitly excluded from EEA, UK, and Switzerland at launch; Computer Use must be enabled on your account or by your org admin. If you're in a supported region with Computer Use enabled, this is worth testing now for repetitive GUI workflows that are currently handled manually.

Affects you ifYou use OpenAI Codex on macOS for agentic tasks with Computer Use enabled; or you are building team automation workflows with Codex and want repeatable, shareable execution paths.EffortQuick (built into the macOS Codex app update; no API changes required).
Medium

AWS Strands Agents: Shell + Evals v1.0 + Context Management — Summit NYC Announcements

What changed
AWS announced three new Strands Agents capabilities at Summit NYC: Strands Shell (sub-millisecond isolated sandbox for file and code access), Strands Evals v1.0.0 (chaos testing + adversarial red teaming framework, released June 16 on GitHub), and context management integrated into the Harness SDK that cuts agent costs in half.
TL;DR
AWS Strands Agents ships three production-hardening capabilities at Summit NYC: sub-ms sandbox launch (Shell), chaos testing + red teaming at build time (Evals v1.0 with five built-in attack strategies), and a context management layer that halves costs — 50M downloads since May open-source launch.
Developer signal
Strands Evals v1.0.0 is the piece with the most immediate developer value — add it to your CI pipeline now. It provides two testing modes: (1) chaos testing via deterministic fault injection using Strands plugin hooks — simulate tool timeouts, network errors, and response corruption without real infrastructure failures; (2) adversarial red teaming using built-in attack strategies (Crescendo, GOAT, PAIR, BadLikertJudge, SequentialBreak) that probe how your agent handles structured adversarial inputs. The framework uses OpenTelemetry traces for behavioral analysis, LLM-as-a-Judge evaluators for quality scoring, and Pydantic schemas for structured outputs; results serialize to JSON for tracking across runs. Repo: github.com/strands-agents/evals. Strands Shell provides an isolated sandbox that launches in under 1ms — fast enough for CI on every commit without adding meaningful build time; this is what makes running chaos tests pre-merge feasible. Context management (Harness SDK) halves agent context costs; the specific implementation approach was not detailed in available sources. If you're building production Strands agents without evals, this is the week to change that.

Affects you ifYou are building agents with the AWS Strands Agent SDK and want pre-deployment reliability testing, adversarial safety coverage, or context cost reduction.EffortModerate (add Strands Evals to your test suite and configure Strands Shell for isolated CI; no breaking changes to the Strands SDK itself).
Notable

llama.cpp b9723: Eagle3 Speculative Decoding Now Supports Qwen 3.5 and 3.6

What changed
llama.cpp adds Eagle3 speculative decoding support for Qwen 3.5 and 3.6 model families, extending the Eagle3 draft framework (previously covering select model families) to Alibaba's latest Qwen generation, plus deferred boundary checkpoint restore for hybrid model architectures.
TL;DR
Qwen 3.5 and 3.6 users on llama.cpp can now use Eagle3 speculative decoding — Eagle-family methods typically deliver 2-4x inference speedup at equivalent output quality vs. standard autoregressive generation.
Developer signal
Eagle3 is the third generation of the Eagle speculative decoding approach, using a lightweight draft model to predict multiple tokens ahead, then verifying them in parallel with the target model. If you're running Qwen 3.5 or 3.6 locally via llama.cpp and have (or can download) the matching Eagle3 draft model weights, update to b9723 and add --draft-model <path-to-eagle3-draft> to your llama-server or llama-cli invocation. The "deferred boundary checkpoint restore" change handles Qwen's hybrid MoE-dense layer architecture — where MoE layers and dense layers alternate — ensuring correct state restoration at layer-type boundaries, which is a correctness fix that also enables the Eagle3 draft to work reliably across the full model. Eagle3 draft model weights for Qwen 3.5/3.6 should be available on Hugging Face; search for Eagle3-Qwen3 variants. No other configuration changes are required beyond the standard speculative decoding setup.

Affects you ifYou are running Qwen 3.5 or Qwen 3.6 models locally via llama.cpp and want significantly faster inference without hardware upgrades.EffortModerate (requires downloading the Eagle3 draft model weights for your Qwen variant and adding --draft-model to your invocation; no other code changes).

Benchmarks & Leaderboards

No leaderboard movements or new SOTA entries confirmed in the June 18-19 window. LMArena standings unchanged from June 17 (last changes: Minimax M3 and GLM 5.2 Max added June 16; Kimi K2.7 Code added June 17 — all covered in prior digests). SWE-bench Verified: unchanged (Claude Mythos 5 at 95.5%, Claude Fable 5 at 95.0% — both models currently suspended under the US export-control directive issued June 12). LiveCodeBench and BigCodeBench: no specific June 18-19 changes confirmed. Kimi K2.7 Code head-to-head Arena voting continues to accumulate — see Worth Watching for expected independent benchmark timeline (~June 22).

Technical Discussions

Nothing cleared the quality bar this period. No Hacker News threads with score >200 for AI developer topics identified in the June 18-19 window. No qualifying technical discussion threads from r/LocalLlama or r/MachineLearning surfaced.

Quick Hits

  • llama.cpp b9716 (June 19, 03:55 UTC) — Adds batching support for InternVL multi-modal model: multiple simultaneous vision inference requests can now run in parallel instead of sequentially. If you run InternVL for high-throughput multi-modal workloads via llama.cpp, this should meaningfully improve throughput. [github.com/ggml-org/llama.cpp/releases]
  • llama.cpp b9717 (June 19, 06:32 UTC) — K-tail support added for Power10 Q8/Q4 MMA (Matrix Multiply Accumulate) matmul: extends POWER10 architecture optimization coverage to edge cases in the matrix multiply kernel. Affects IBM Power10 server deployments running quantized models. [github.com/ggml-org/llama.cpp/releases]
  • llama.cpp b9728 (June 19, 16:19 UTC) — Comment line support added to --api-key-file: #-prefixed lines are now ignored when parsing the API key file. Useful for documenting multi-key configurations or temporarily disabling keys. [github.com/ggml-org/llama.cpp/releases]

Worth Watching (Announced, Not Yet Shipped)

12

⚠️⚠️⚠️ Gemini API Unrestricted Key Deadline — **TODAY (June 19) — ACTIVE NOW**

(Deadline has arrived — no grace period)

All unrestricted Gemini API keys are blocked as of today. Restrict via AI Studio → API Keys → "Restrict to Gemini API" — takes ~2 minutes, no code changes required. If your pipeline is returning unexpected auth errors today, this is the most likely cause.

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

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

(Countdown updated)

gemini-3.1-flash-image-preview and gemini-3-pro-image-preview shutting down June 25. Migrate to stable image model equivalents.

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

(Countdown updated)

GPT-4.5 removed from the 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

⚠️⚠️ Kimi K2.7 Code Third-Party Benchmarks — **Expected ~June 22 (3 days)**

(Status unchanged — Arena head-to-head voting accumulating)

Weights released June 12, Arena leaderboard entry June 17. Third-party SWE-bench Verified and LiveCodeBench evals typically appear 7–14 days post-weights. Watch paperswithcode.com and swebench.com around June 22-25.

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

(Status unchanged)

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

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

(Status unchanged)

Both models remain suspended under the US export-control directive issued June 12. No return date. 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 general availability date confirmed.

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

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.

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

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

(Countdown updated)

Export eval configs before October 31 (read-only from that date). 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.