← All digests
AI Developer Digest

Mon, Jun 15, 2026

18 signals that cleared the gate22 min read
The Signal — start here
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 today
1
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
2
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 Changes

2
●Breaking

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

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 ifYou are calling model: "claude-sonnet-4-20250514" or model: "claude-opus-4-20250514" anywhere — production, CI/CD, staging, scripts, or Claude Code auto-mode configEffortQuick (swap the model ID string; verify adaptive thinking behavior if you used manual thinking.budget_tokens; test prompts that use assistant-turn prefills)
●Breaking

Anthropic Agent SDK Billing Split — Effective June 15, 2026

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 ifYou 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 keyEffortModerate (configure billing in Anthropic Console; audit pipeline token consumption; consider migrating heavy automation to a direct pay-as-you-go API key)
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)https://thenewstack.io/anthropic-agent-sdk-credits/ (official Anthropic billing configuration: Anthropic Console → Settings → Billing → Usage Credits)

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

1
Notable

Anthropic SDK Python v0.109.2 — Retired Model IDs Removed

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 ifYou 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 codebaseEffortQuick (pip install --upgrade anthropic, update model ID strings)
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.2https://github.com/anthropics/anthropic-sdk-python/releases/tag/v0.109.2 (commit d4bcfcc257bd0c97d5e75060bd19c97abddd9f49)

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

1
Medium

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

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 ifYou 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 LangFlowEffortQuick (version bump; validate MCP rate limit configs if you enable that feature; test Kubernetes preStop hook behavior in staging)
BerriAI/litellm on GitHub | Date: June 14, 2026 (00:05 UTC) | Link: https://github.com/BerriAI/litellm/releases/tag/v1.89.0https://github.com/BerriAI/litellm/releases/tag/v1.89.0

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.

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)

13

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

(Countdown updated — this is the most time-sensitive item in the digest)

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)

All unrestricted Gemini API keys blocked June 19. Restrict via AI Studio → API Keys → "Restrict to Gemini API." ~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 (10 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 (12 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.

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

⚠️⚠️ 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)

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)

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.

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)**

(Carried — status unchanged)

iOS 27, iPadOS 27, macOS Golden Gate ship September 2026. 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 (169 days)**

(Carried)

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.

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