📡

AI Developer Digest

Mon, Jun 15, 2026

5 items passed quality gate | ~35 scanned | ~30 excluded | Sources checked: 24 Scan window: June 14–15, 2026 (24h). Today is a mandatory action day for Anthropic users: the two breaking changes telegraphed in prior digests are now live. The only net-new technical story is LiteLLM v1.89.0 (June 14), which adds enterprise agent integrations and per-MCP-server rate limiting.

This Week's Signal

Two Anthropic breaking changes hit simultaneously on June 15 — both pre-announced but now enforced: claude-sonnet-4-20250514 and claude-opus-4-20250514 now return errors on every call, and the Agent SDK billing split is active, moving automated agent usage out of the flat subscription and into a separate monthly credit pool. The only new technical development in the window is LiteLLM v1.89.0, which adds Watsonx Orchestrate and LangFlow A2A bridging as agent providers — a signal that LLM gateways are evolving from model routers into enterprise agent orchestration hubs. For most developers, today is a migration audit day, not a feature day.

Must-reads this digest:

claude-sonnet-4-20250514 and claude-opus-4-20250514 now return errors — migrate immediately — all API calls to these model IDs fail as of today; replace with claude-sonnet-4-6 and claude-opus-4-8
Agent SDK billing split is live — claude -p, Claude Code GitHub Actions, and third-party Agent SDK apps now draw from a separate monthly credit; unclaimed or exhausted credit stops automated pipelines cold

[BREAKING] Breaking Changes

[BREAKING] Claude Sonnet 4 and Opus 4 Retired — Effective June 15, 2026

Source: Anthropic Platform Release Notes | Date: June 15, 2026 | Link: https://platform.claude.com/docs/en/release-notes/overview What changed: claude-sonnet-4-20250514 and claude-opus-4-20250514 moved from deprecated to retired. All API requests to either model ID now return an error. Researchers needing these specific weights can apply via the External Researcher Access Program. TL;DR: As of June 15, calling claude-sonnet-4-20250514 or claude-opus-4-20250514 returns an error — replacements are claude-sonnet-4-6 (alias for claude-sonnet-4-6-20260217) and claude-opus-4-8. Developer signal: Audit every environment where these model IDs appear. Priority locations: .env files, CI/CD pipeline configs, Kubernetes secrets, hardcoded model= parameters in API clients, and any LiteLLM proxy configs or OpenRouter aliases pointing to these IDs. The replacement models use adaptive thinking instead of manual thinking.budget_tokens parameters — if your code set a manual thinking budget, verify prompt behavior with the adaptive model before deploying. The 4.6+ models also reject assistant-turn prefills; if your prompts use prefill injection as a technique, test for regressions. For researchers needing the original weights, apply via the External Researcher Access Program linked in the Anthropic model deprecations page. Affects you if: You are calling model: "claude-sonnet-4-20250514" or model: "claude-opus-4-20250514" anywhere — production, CI/CD, staging, scripts, or Claude Code auto-mode config Adoption effort: Quick (swap the model ID string; verify adaptive thinking behavior if you used manual thinking.budget_tokens; test prompts that use assistant-turn prefills) Primary source: https://platform.claude.com/docs/en/release-notes/overview — also confirmed at https://platform.claude.com/docs/en/about-claude/model-deprecations Quality gate score: 9 (official Anthropic release notes +3, specific model IDs and concrete error behavior documented +2, changelog as primary source +2, within scan window +1, technical audience +1)

[BREAKING] Anthropic Agent SDK Billing Split — Effective June 15, 2026

Source: Anthropic (billing announcement, Help Center) | Date: June 15, 2026 | Link: https://thenewstack.io/anthropic-agent-sdk-credits/ (secondary — official: Anthropic Console → Settings → Billing → Usage Credits) What changed: Prior to June 15, usage via claude -p (headless), Claude Code GitHub Actions, and third-party apps built on the Agent SDK was covered by the flat Claude subscription. From June 15, these automated paths draw from a separate monthly credit pool billed at standard API rates: approximately $20/month for Pro, $100/month for Max 5x, $200/month for Max 20x. When the credit is exhausted, automated requests stop unless overflow billing is enabled. Credits are per-user, not team-pooled, and do not roll over between billing cycles. TL;DR: The Agent SDK credit pool is now active — Pro subscribers get ~$20/month of API-rate credit for automated agent usage; exhausted credit halts pipelines unless overflow billing is activated in the Anthropic Console. Developer signal: Four immediate actions: (1) Claim your credit — Anthropic sent claim emails around June 8; if yours didn't arrive, navigate to Claude Account Settings and look for the Agent SDK Credit section and claim it there. (2) Enable overflow billing — in Anthropic Console → Settings → Billing → Usage Credits, enable overflow so automated requests don't hard-stop when the monthly credit runs out; overflow charges at standard API rates. (3) Estimate your pipeline cost — the ~$20 Pro credit covers roughly 100K tokens at Opus 4.8 rates or ~20M tokens at Haiku 4.5 rates at standard pricing; heavy automated workloads will exhaust this in hours or days. (4) Migrate heavy automation to a direct API key — developers who already call the Anthropic API directly with a pay-as-you-go key (not through the subscription path) are unaffected by this change. If you run heavy claude -p pipelines, moving to a direct ANTHROPIC_API_KEY with a dedicated pay-as-you-go account gives cleaner cost accounting. Interactive chat usage is NOT affected. Affects you if: You run claude -p in scripts or CI; you use Claude Code GitHub Actions via the subscription path; you use third-party apps built on the Agent SDK; you haven't already separated heavy automated usage onto a direct API key Adoption effort: Moderate (configure billing in Anthropic Console; audit pipeline token consumption; consider migrating heavy automation to a direct pay-as-you-go API key) Primary source: https://thenewstack.io/anthropic-agent-sdk-credits/ (official Anthropic billing configuration: Anthropic Console → Settings → Billing → Usage Credits) Quality gate score: 7 (official Anthropic announcement covered by primary tech press +3, specific credit amounts and activation steps confirmed across multiple sources +2, within scan window +1, technical audience +1)

Model Releases

No new model releases in the June 14–15 scan window. Gemini 3.5 Pro remains in limited Vertex enterprise preview with no GA announcement. Kimi K2.7 Code weights landed June 12 (outside window) — third-party benchmarks still pending. See Worth Watching for upcoming releases.

API & SDK Changes

[NOTABLE] Anthropic SDK Python v0.109.2 — Retired Model IDs Removed

Source: anthropics/anthropic-sdk-python on GitHub | Date: June 15, 2026 (17:30 UTC) | Link: https://github.com/anthropics/anthropic-sdk-python/releases/tag/v0.109.2 What changed: Removed claude-sonnet-4-20250514 and claude-opus-4-20250514 from the SDK's typed model ID enum (commit d4bcfcc). Prior SDK versions still listed these as valid ModelParam constants at the type level, even though the API now returns errors for them. TL;DR: SDK v0.109.2 removes retired model ID constants from the Python type system — upgrade to catch stale model references as type errors at the call site rather than runtime API errors. Developer signal: Run pip install --upgrade anthropic to get v0.109.2. If your code references claude-sonnet-4-20250514 or claude-opus-4-20250514 as typed anthropic.types.ModelParam constants (rather than raw strings), upgrading will surface a Python type error at the call site — this is intentional and serves as a compile-time flag to update your model IDs. If you use raw strings, the SDK upgrade itself is safe; you'll still get the runtime error from the API until you swap the string. There are no other changes in this release. Affects you if: You use the anthropic Python SDK and reference the retired model IDs as typed SDK constants; or you want compile-time enforcement that retired model strings are removed from your codebase Adoption effort: Quick (pip install --upgrade anthropic, update model ID strings) Primary source: https://github.com/anthropics/anthropic-sdk-python/releases/tag/v0.109.2 (commit d4bcfcc257bd0c97d5e75060bd19c97abddd9f49) Quality gate score: 9 (official Anthropic GitHub +3, specific commit and code change confirmed +2, GitHub as primary source +2, within scan window +1, technical audience +1)

Research

Nothing cleared the quality bar this period. The arXiv cs.AI and cs.CL listing pages returned HTTP 403, blocking direct enumeration of June 15 submissions. Two paper candidates surfaced in search snippets — "GRPO Does Not Close the Multi-Agent Coordination Gap" and "BAGEN: Are LLM Agents Budget-Aware?" — but neither had confirmed benchmark numbers or associated code repos verifiable from available sources. See Near-misses below.

Tooling

[MEDIUM] LiteLLM v1.89.0 — Watsonx Orchestrate, LangFlow A2A, Per-Server MCP Rate Limiting, Kubernetes Drain

Source: BerriAI/litellm on GitHub | Date: June 14, 2026 (00:05 UTC) | Link: https://github.com/BerriAI/litellm/releases/tag/v1.89.0 What changed: Weekly minor version release (from v1.88.x). Adds two new enterprise agent provider integrations (Watsonx Orchestrate, LangFlow with A2A session bridging), per-MCP-server RPM rate limiting scoped to API keys and teams, native Kubernetes graceful shutdown via /health/drain, and OpenInference observability parity for Arize/Phoenix. Fixes include Vertex AI Haiku 4.5 output_config.effort stripping, PostgreSQL NUL byte corruption in spend logs, and Datadog batch requeue loop on 413 errors. TL;DR: LiteLLM v1.89.0 adds Watsonx Orchestrate and LangFlow A2A as agent providers, per-MCP-server RPM limits for teams, and /health/drain Kubernetes preStop hook support — no benchmark data, feature/fix release only. Developer signal: Five specific changes worth evaluating for your setup: (1) MCP per-server rate limiting — you can now set per-server RPM limits scoped to API keys or teams, and per-server environment variables at global and per-user scopes. If you share MCP tool servers across teams via the LiteLLM proxy, this resolves the common issue of one team's tool calls exhausting shared server capacity. (2) Kubernetes graceful drain — add /health/drain as your pod's preStop hook; it properly drains in-flight requests before termination, replacing the sleep 15 workaround common in LiteLLM Helm deployments. (3) Vertex AI Haiku 4.5 fix — output_config.effort is now correctly stripped before sending to Vertex, fixing 400 errors introduced when Haiku 4.5 launched. If you're on Vertex with Haiku 4.5 and seeing 400s, this is your fix. (4) Arize/Phoenix observability — OpenInference traces now include tool calls, cost attribution, passthrough I/O, session/user metadata, multimodal, and cache token fields that were previously missing. (5) Agent providers — if you're integrating Watsonx Orchestrate or LangFlow workflows into a LiteLLM gateway, these are now first-class providers with A2A session bridging for LangFlow. Upgrade: pip install litellm==1.89.0. Affects you if: You run LiteLLM as a model proxy or gateway; you use MCP tool servers through LiteLLM with multi-team access; you deploy LiteLLM on Kubernetes; you use Vertex AI Haiku 4.5; you trace with Arize Phoenix/OpenInference; you integrate Watsonx Orchestrate or LangFlow Adoption effort: Quick (version bump; validate MCP rate limit configs if you enable that feature; test Kubernetes preStop hook behavior in staging) Primary source: https://github.com/BerriAI/litellm/releases/tag/v1.89.0 Quality gate score: 9 (official GitHub source +3, concrete code and technical changes documented +2, GitHub as primary source +2, within scan window +1, technical audience +1)

Benchmarks & Leaderboards

No new leaderboard movements or SOTA changes in the June 14–15 scan window. Most recent additions (Claude Fable 5 on LMArena June 10, Nemotron 3 Ultra on Agent Arena June 12) are outside the window and were covered in prior digests. Third-party SWE-bench Verified and LiveCodeBench evaluations for Kimi K2.7 Code are pending — expected around June 22.

Trends & Emerging Tech

ChatGPT "Dreaming" Memory Reaches Free Tier — Product Signal for Stateful Agent Patterns

Source: OpenAI Blog | Date: June 14, 2026 | Link: https://openai.com/blog What's happening: OpenAI published "Better memory for a more helpful ChatGPT" on June 14, announcing broader availability of the "Dreaming" memory architecture (which began rolling out to Plus/Pro on June 4). Dreaming is an asynchronous background process that synthesizes memory across a user's full conversation history, including temporal self-correction: a stored memory like "you're going to Singapore in July" auto-rewrites to "you went to Singapore in July 2026" after the trip ends, with no user action. The June 14 post extends this to US Free tier users and signals international rollout is underway. Why watch this: This is a ChatGPT product-level feature, not an API change — the Assistants and Responses APIs are unchanged. However, the architectural pattern (async background synthesis, temporal awareness, no explicit user upserts) is now shipping at scale in a major product, and it demonstrates a capability that developer-built memory systems (vector DBs, explicit key-value stores) don't match: automatic staleness correction. If OpenAI moves this pattern into the API tier as a memory management primitive, it would significantly change how persistent-context agent applications are built. The near-term signal: watch the Assistants API thread and memory tooling roadmap. In the meantime, developers building stateful agent memory can implement a simplified version of the temporal awareness pattern — memory entries with valid_until fields and periodic re-synthesis jobs — using existing backends.

Technical Discussions

Nothing cleared the quality bar this period.

Quick Hits

llama.cpp b9645–b9655 (June 15, 14:41–19:55 UTC) — 9 builds in ~5 hours: Metal bf16 repeat support (b9645), SYCL Level Zero per-initialization rather than per-allocation driver checks for Intel GPU (b9646), SYCL pool_1d support with ops.md docs (b9647), SYCL softmax reduction and reorder function fixes (b9649-b9650), SYCL native subgroup size for K-quant DMMV (b9651), WASM fallback symbol collision fix (b9652), Vulkan expanded CONCAT type support (b9653), mtmd post-decode callback for multi-threaded multi-device (b9654), grammar generator "oldie but goodie" bug fix (b9655). No new model support, no new hardware platforms, no performance benchmarks published. Backend maintenance and Intel SYCL optimization focus. [https://github.com/ggml-org/llama.cpp/releases]
LiteLLM v1.88.2, v1.87.3, v1.86.6 (June 14, 01:04–02:51 UTC) — Three maintenance backport releases to stable branches (1.88.x, 1.87.x, 1.86.x). Backported: Fable 5 model support, batch-file auth fixes, CrowdStrike AIDR integration, Mantle Responses SigV4, database resilience patches. No new features; these track v1.89.0 fixes to stable branch users. [https://github.com/BerriAI/litellm/releases]

Worth Watching (Announced, Not Yet Shipped)

⚠️⚠️⚠️ Gemini CLI Hard Stop — June 18 (3 DAYS — URGENT)

(Countdown updated — this is the most time-sensitive item in the digest) Source: Google Developers Blog | Link: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/ The gemini CLI and Gemini Code Assist IDE extensions stop serving requests on June 18 for Google AI Pro, Google AI Ultra, and free-tier (Code Assist for individuals) users. Hard stop — no grace period. Replacement is agy (Antigravity CLI, Go binary). Key caveats: Antigravity does NOT have 1:1 feature parity with Gemini CLI at launch; the weekly compute-based cap replaces the 1,000 req/day limit with a unit that heavy users report exhausting quickly, with multi-day cooldowns when it runs out. Google Cloud org accounts on Standard or Enterprise license are not affected. Audit all CI/CD pipelines, GitHub Actions workflows, and scripts that call the gemini command before Thursday morning.

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

(Countdown updated) Source: Google AI for Developers | Link: https://ai.google.dev/gemini-api/docs/api-key All unrestricted Gemini API keys blocked June 19. Restrict via AI Studio → API Keys → "Restrict to Gemini API." ~2 minutes; no code changes required.

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

(Countdown updated) Source: Google AI for Developers | Link: https://ai.google.dev/gemini-api/docs/deprecations 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 (12 days)

(Countdown updated) Source: OpenAI Platform Changelog | Link: https://platform.openai.com/docs/changelog GPT-4.5 removed from the ChatGPT product surface June 27. API route retirement unconfirmed. Audit any gpt-4.5 model identifiers.

⚠️⚠️ Kimi K2.7 Code Third-Party Benchmarks — Expected ~June 22

(Carried from prior digest) Kimi K2.7 Code weights landed June 12. Third-party SWE-bench Verified and LiveCodeBench evaluations typically appear 7–14 days post-weight release. Community skepticism about vendor-proprietary benchmark claims. Watch paperswithcode.com and swebench.com around June 20–25.

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

(Status unchanged since June 14 digest) 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 benchmark numbers for public access. Mid-June API release window is still open but no announcement as of June 15.

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

(Carried) Source: Anthropic | Link: https://www.anthropic.com/news/fable-mythos-access Both models suspended June 12 under US export-control directive. Anthropic is publicly disputing the directive's factual basis while complying. No return date. Migrate to claude-opus-4-8 for agentic workloads.

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

(Carried — status unchanged) Source: Google AI for Developers | Link: https://ai.google.dev/gemini-api/docs/models Expected: 2M token context, Deep Think reasoning mode. In limited Vertex AI Model Garden preview for enterprise accounts. No general availability date. Expected imminently based on Google I/O announcement timeline.

⚠️ Aion 1.0 Open Weights — July 2026 (~2–3 weeks)

(Countdown updated) Source: Windows Developer Blog | Link: https://blogs.windows.com/windowsdeveloper/2026/06/02/build-2026-furthering-windows-as-the-trusted-platform-for-development/ Microsoft Aion 1.0 Instruct open weights on Hugging Face in July 2026. No confirmed specific date.

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

(Countdown updated) Source: Anthropic | Link: https://platform.claude.com/docs/en/about-claude/model-deprecations claude-opus-4-1-20250805 retires August 5. Migrate to claude-opus-4-8.

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

(Carried — status unchanged) Source: Apple Developer / WWDC 2026 | Link: https://developer.apple.com/ios/ iOS 27, iPadOS 27, macOS Golden Gate ship September 2026. Includes: Siri Extensions API, Core AI (replaces Core ML), Foundation Models multi-provider support.

Claude Mythos 5 General Availability — No Timeline

(Carried — suspended under same export-control order; GA timeline unknown) Source: Anthropic | Link: https://www.anthropic.com/news/expanding-project-glasswing

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

(Carried) Source: OpenAI | Link: https://platform.openai.com/docs/deprecations Three products deprecated June 3. 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.

<details> <summary>🔭 Horizon — Open Questions, Emerging Patterns & Grounded Speculation</summary>

This section operates under different rules than the digest above. Evidence-grounded speculation is allowed. Pure prediction is not. Every claim here must cite a source from this digest or a real paper/benchmark. Label each entry by type so the reader knows what kind of thinking they're engaging with.

[PATTERN] LLM gateways are absorbing enterprise agent orchestration infrastructure LiteLLM v1.89.0's addition of Watsonx Orchestrate and LangFlow A2A bridging continues a pattern visible across the v1.8x release series: the gateway isn't just routing model requests anymore, it's becoming the convergence point for heterogeneous agent systems. Watsonx Orchestrate is IBM's enterprise workflow orchestrator; LangFlow is a visual agent builder; A2A bridging means LiteLLM can now route between agent execution environments through the same proxy it uses for model routing. This follows earlier additions of AutoGen, CrewAI, and smolagents as agent providers. The trend line: as enterprise agent frameworks proliferate, the LLM gateway is becoming the normalize-and-route layer — not any individual framework. Watch for LiteLLM adding memory-layer integrations (Mem0, Zep) as the next signal that the gateway is becoming the full agent infrastructure hub. Grounded in: LiteLLM v1.89.0 agent provider additions (this digest, Tooling); LiteLLM v1.85.0 routing groups (prior digests)

[TENSION] Billing separation reduces the barrier to agent adoption while raising the cost of agent experimentation Anthropic's Agent SDK billing split (live today) separates automated agent usage from subscription usage — financially logical as agent workloads scale, but it creates a new friction for developers who used the flat subscription as a cost-free dev environment for agent experiments. The ~$20/month Pro credit covers roughly 100K tokens at Opus 4.8 rates — less than an hour of heavy agentic experimentation with a complex multi-step agent. Developers who previously ran claude -p freely during prototyping now need to enable overflow billing (and accept charges) or budget their experiments more carefully. The tension: Anthropic's roadmap is explicitly centered on agents, but this billing change disincentivizes casual agent experimentation precisely in the developer tier most likely to experiment and build new applications. This mirrors how OpenAI's June 2 container billing change worked — a logical cost-allocation move that adds friction at the exploration phase. Grounded in: Agent SDK billing split (this digest, [BREAKING]); ~$20 Pro credit amount and API rate implications (this digest, [BREAKING]); OpenAI container billing June 2 (prior digest context)

[OPEN QUESTION] When does the platform maintenance cadence become a reliability tax that changes the build vs. buy calculation? Today's double breaking change (Sonnet 4 / Opus 4 retirement + Agent SDK billing split) is the fourth disruptive Anthropic event in 72 hours, following the Fable 5 suspension (June 12), Agent SDK billing announcement, and Sonnet 4 / Opus 4 retirement warning. Looking broader: Google kills Gemini CLI in 3 days. OpenAI deprecated three products in one day on June 3. The aggregate picture for any team with more than two AI provider integrations: a substantial and growing "platform maintenance tax" — model retirements, billing changes, CLI migrations, sudden suspensions, API key restrictions. The open question: is there a threshold at which this maintenance burden makes provider-agnostic abstraction layers (LiteLLM, OpenRouter, a custom wrapper) a compliance requirement rather than a performance optimization — not because you want to switch models, but because you can't afford another zero-notice migration? Grounded in: Claude Sonnet 4 / Opus 4 retirement (this digest, [BREAKING]); Agent SDK billing split (this digest, [BREAKING]); Fable 5 suspension June 12 (June 14 digest); Gemini CLI shutdown June 18 (this digest, Worth Watching); OpenAI triple deprecation June 3 (prior digest)

[IF THIS CONTINUES] Per-server MCP rate limiting signals MCP is now production infrastructure, not a demo layer LiteLLM v1.89.0 adds per-MCP-server RPM limits scoped to API keys and teams, plus per-server environment variables. Six months ago, MCP was primarily used in development contexts where unlimited tool access was expected. The need for per-server rate limiting implies MCP tool servers are now shared across teams with real cost and abuse potential — you don't rate-limit things that only one person touches. If this pace continues — per-server env vars, per-server rate limits, per-user scoping, OAuth token persistence (all in this release) — LiteLLM will functionally become an MCP orchestration platform within a quarter, layered atop its existing model proxy role. The signal to watch: per-server audit logging and per-server authentication in future releases would confirm this trajectory. The practical implication: teams evaluating MCP for production multi-team deployments should now be evaluating LiteLLM as the access control layer, not just the model router. Grounded in: LiteLLM v1.89.0 MCP rate limiting and env vars (this digest, Tooling)

[BUILDER'S ANGLE] The Dreaming pattern as an extractable template for stateful agent memory OpenAI's Dreaming system (June 14 blog) demonstrates temporal self-correction at scale: memories that auto-update as facts age, without user prompts. This is a genuinely hard problem for developer-built agent memory systems — vector DB entries and key-value stores don't update themselves when the world changes. A memory that says "user's project deadline is July 15" becomes stale on July 16 with no mechanism to detect or correct this. Dreaming's approach — background synthesis jobs that periodically re-read recent conversations and update the memory store with temporal awareness — is currently a ChatGPT product feature, not an API primitive. But the pattern is extractable: (1) a periodic background job that re-reads recent conversations and compares to the existing memory store; (2) memory entries with an event_date or valid_until field that triggers re-synthesis after the date passes; (3) a staleness scorer that flags entries for review. Developers building persistent-context agent systems who are ahead of any potential API-tier Dreaming equivalent can implement this three-component pattern now using existing infrastructure (any vector DB + a scheduled job + a short-context LLM call for re-synthesis). The cost is low; the payoff is agents that don't confidently surface stale facts. Grounded in: OpenAI Dreaming June 14 blog (this digest, Trends & Emerging Tech); current Assistants API memory model (explicit upserts only, no automatic staleness correction)

</details>

Excluded: ~30 items below quality gate threshold, outside scan window, or already covered in prior digests. Near-misses: Phi-4-reasoning-vision-15B (March 4, 2026 — well outside window); Unsloth v0.1.464-beta with DiffusionGemma/MiniMax-M3 support (June 12, 2026 — outside 24h window, technically significant, consider for next digest if not yet covered); LMArena: Claude Fable 5 added June 10, Nemotron 3 Ultra added June 12 (both outside window); SWE-bench Pro last update June 9 (outside window); Nathan Lambert "My bets on open models, mid-2026" (fetch returned 403 — content unverifiable, title suggests prediction piece rather than concrete research); arXiv cs.AI/cs.CL listing pages (403 on all fetch attempts — June 15 submissions unverifiable; "GRPO Does Not Close the Multi-Agent Coordination Gap" and "BAGEN: Are LLM Agents Budget-Aware?" surfaced in search snippets but no code repos or benchmark numbers confirmed); OpenAI GPT-Realtime-2 / GPT-Realtime-Translate / GPT-Realtime-Whisper (appeared in OpenAI changelog June 2026 but date within scan window unconfirmed — cannot verify June 14-15 publication); OpenAI return_token_budget feature for Responses API web search (same date ambiguity); Gemini 3.5 Pro (no GA or new access announcement in window, still limited Vertex preview); OpenAI Academy courses June 14 (education, not developer tooling); NVIDIA Ising quantum AI models (interesting but niche, date unconfirmed); Groq blog (no new post in window); Together AI blog (no new post in window); AWS Bedrock (no June 14-15 post confirmed); Azure AI blog (no June 14-15 post confirmed); Fireworks AI (no new post in window); Simon Willison June 14 "Why AI hasn't replaced software engineers" (link post to opinion piece — no primary source for a new release, score: 1); Simon Willison June 15 Julia Evans quote (not AI developer news); Hacker News (no qualifying thread with score >200 and technical depth confirmed in window); r/LocalLlama, r/MachineLearning (no qualifying posts confirmed in window).

← All digestspersonal/digests/ai-2026-06-15.md