← All digests
AI Developer Digest

Tue, Jun 23, 2026

17 signals that cleared the gate24 min read
The Signal — start here
June 23 is a platform-layer day rather than a model-release day. Anthropic launched Claude Tag (research preview), a persistent AI teammate embedded directly in Slack that works autonomously across channels — Anthropic's first dedicated workplace agent product. OpenAI expanded Daybreak with the full GPT-5.5-Cyber release, a Codex Security plugin embedded in developer workflows, a 20+ vendor Cyber Partner Program, and the Patch the Planet initiative targeting cURL, Go, Python, and other critical open-source projects. Both announcements signal the same shift: the frontier labs are now competing at the application and deployment layer, not just the model layer. Local inference continues its steady cadence: llama.cpp b9763 ships an OpenAI Responses API compliance fix (missing id field on tool call outputs was breaking Rig 0.39 and other frameworks) and b9768 adds Granite Speech Plus model support.
Must-reads today
1
Claude Tag — Anthropic's first persistent Slack-native AI coworker, research preview for Claude Enterprise and Team customers; signals the shift from session-based assistant to always-on agent in team workflows
2
Daybreak expanded + GPT-5.5-Cyber full release — 85.6% on CyberGym (vs 81.8% for standard GPT-5.5), Codex Security plugin in dev workflows, Patch the Planet with cURL/Go/Python as initial open-source targets; the most complete cybersecurity AI deployment stack announced to date
3
llama.cpp b9763 — tool call response id field added to align with OpenAI Responses API spec; upgrade now if you use Rig, or any OpenAI-spec client that deserializes /v1/responses tool call outputs from llama-server

Breaking Changes

No breaking changes this period.

Model Releases

1
Medium

OpenAI GPT-5.5-Cyber Full Release — Daybreak Expands with Codex Security and Patch the Planet

What changed
GPT-5.5-Cyber moved from limited-preview (May 7 Daybreak launch, vetted-only) to full release for verified defenders and Daybreak Cyber Partners. June 22 additions: full GPT-5.5-Cyber rollout to authorized defenders, Codex Security plugin embedded directly in developer workflows, Daybreak Cyber Partner Program launched with 20+ security vendors (Accenture, Akamai, Check Point, Cisco, Cloudflare, CrowdStrike, IBM, Palo Alto Networks among initial partners), and Patch the Planet — a program founded with Trail of Bits + HackerOne to fix vulnerabilities in widely-used open-source projects; >30 OSS projects committed with cURL, Go, Python, Sigstore, and pyca/cryptography as initial participants.
TL;DR
GPT-5.5-Cyber hits 85.6% on CyberGym (vs 81.8% for GPT-5.5 standard, vs 73.1% for Claude Opus 4.7), 39.5% on ExploitGym (vs 25.95% for GPT-5.5), and 69.8% on SEC-bench Pro (vs 63.1% for GPT-5.5) — now accessible to verified defenders and Cyber Partner organizations via the Daybreak program.
Developer signal
If you work in a security product or service company, apply to the Daybreak Cyber Partner Program — approved partners can embed GPT-5.5 with Trusted Access for Cyber in their products. For most organizations, GPT-5.5 with Trusted Access for Cyber is the recommended entry point; GPT-5.5-Cyber itself remains gated to defenders responsible for critical infrastructure. The Codex Security plugin is the more broadly accessible piece: it embeds AI-assisted vulnerability detection directly in the development workflow, meaning the practical entry point for most developer teams is the Codex integration rather than direct GPT-5.5-Cyber API access. No direct public API model ID for GPT-5.5-Cyber was published; access flows through the Trusted Access for Cyber program with verified enrollment. Patch the Planet is a model for AI-assisted open-source maintenance — worth monitoring if you maintain or depend on widely-used open-source libraries, as AI-generated patches will start appearing in PRs on repos like cURL, CPython, and pyca/cryptography.

Affects you ifYou build security products or services and want to embed GPT-5.5-level capability for cybersecurity workflows; or you maintain critical open-source infrastructure and expect to receive (or want to participate in) AI-generated security patches from the Patch the Planet initiative.EffortSignificant (Daybreak Cyber Partner Program enrollment required; GPT-5.5-Cyber access is gated; Codex Security plugin setup follows standard Codex integration path).

API & SDK Changes

No new stable API or SDK changes in the June 22–23 scan window.

  • Anthropic platform release notes: last entry June 15, 2026 (Claude Sonnet 4 / Opus 4 retirement — covered in prior digests).
  • OpenAI platform changelog: June 22's Daybreak announcement is a product launch, not an API changelog entry. No new API-level entries on June 22–23.
  • Gemini API changelog: last entry 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 returned HTTP 403 on direct list fetch (consistent with prior digests). HuggingFace Papers returned 403. Search-based fallback 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 submitted June 22–23. Highest-numbered arXiv IDs found in search were in the 2606.22xxx range; none passed the minimum quality gate criteria (recognized lab + code repository + measurable benchmark numbers).

Tooling

3
Medium

Anthropic Claude Tag: Persistent AI Teammate Launches in Slack (Research Preview)

What changed
Anthropic launched Claude Tag in research preview — a Slack-native AI agent that persists across channels and operates proactively, not just when invoked. Unlike previous Claude integrations that required a fresh context per conversation, Claude Tag maintains organizational context over time, can be summoned via @Claude in any thread, breaks tasks into verifiable stages and works through them autonomously, and proactively flags relevant updates across the organization.
TL;DR
Claude Tag is Anthropic's first always-on AI teammate product — a Slack agent that reads channels, decomposes tasks, executes them autonomously in stages, and surfaces relevant information proactively; available in research preview for Claude Enterprise and Claude Team customers, with plans to expand to other platforms.
Developer signal
If your organization is on Claude Enterprise or Claude Team, you can apply for the Claude Tag research preview today. The key architectural difference from prior integrations: Claude Tag is an asynchronous agent with persistent context, not a synchronous chatbot. When assigned a task via @Claude, it breaks it into stages, executes independently, and delivers results to the thread — meaning you can hand off multi-step work and not supervise each step. Administrators have per-channel controls over what data and tools Claude Tag can access, which is important for governing what organizational context the agent reads. No public API or webhook integration spec was published with this launch; this is currently a product-layer integration for Slack customers, not an SDK release. Anthropic noted wider platform rollout is planned in the coming weeks. Watch for Teams and other messaging platforms as the next targets.

Affects you ifYou manage AI tooling for a Claude Enterprise or Claude Team organization; or you are building team productivity workflows on top of Anthropic's APIs and want to understand the product direction for persistent agentic context.EffortModerate (Claude Enterprise/Team subscription required; research preview sign-up; per-channel access control configuration needed before deployment).
Medium

llama.cpp b9763: Tool Call Response `id` Field — OpenAI Responses API Spec Compliance Fix

What changed
Added the missing id field to /v1/responses tool call output items in llama-server (PR #24882). Previously, llama-server emitted only call_id (the tool call correlation ID) on function call output objects. OpenAI's documented Responses API spec requires both id (item-level function-call output identifier) and call_id. Clients implementing strict deserialization against the OpenAI spec — specifically confirmed for Rig 0.39 — failed with "missing field id" errors.
TL;DR
llama-server's /v1/responses endpoint was non-compliant with OpenAI's function-calling spec by missing the id field on tool call output items; b9763 adds it, fixing deserialization failures in Rig 0.39 and any other client that expects the full OpenAI-compliant response structure.
Developer signal
Update to b9763 if you use llama-server's /v1/responses endpoint with any OpenAI-spec client library that deserializes tool call outputs. The failure mode is a runtime deserialization error ("missing field id"), not a graceful degradation — it silently breaks tool use in affected frameworks. Rig 0.39 is the confirmed example, but any client written against the OpenAI Responses API function-calling reference (which includes both id and call_id on output items) would exhibit the same failure. If you built a custom client against llama-server and it has been working, check whether your deserialization code was silently dropping the id field or using optional fields — the correct behavior after b9763 is to consume both fields. No changes to API call structure required; this is a server-side response fix only.

Affects you ifYou call llama-server's /v1/responses endpoint and use tool calls, and your client library does strict deserialization against the OpenAI Responses API spec (Rig, or any client that treats id as a required field on function call output items).EffortQuick (update to b9763; no client code changes required — the missing field is now present in server responses).
Notable

llama.cpp b9768: Granite Speech Plus Model Support Added

What changed
Added conversion support for the Granite Speech Plus model (IBM, PR #24818). The implementation extends the granite_speech module to support multi-layer concatenation — a feature required by the Granite Speech Plus architecture beyond the base Granite Speech model. Also standardizes feature_layers naming across audio processing components for consistency. Co-developed by Gabe Goodhart and Xuan-Son Nguyen.
TL;DR
llama.cpp can now convert and run IBM Granite Speech Plus models locally — the "Plus" architecture variant that uses multi-layer audio feature concatenation was previously unsupported.
Developer signal
If you use IBM Granite Speech models for speech-to-text or audio processing workflows locally, update to b9768 to access Granite Speech Plus. The conversion tooling is the primary addition — the inference path extends the existing Granite Speech implementation. No benchmark numbers were published with this release; you will need to evaluate Granite Speech Plus vs base Granite Speech quality on your own data. Granite Speech Plus is part of IBM's enterprise speech AI stack and is relevant if you are integrating on-premise or edge speech processing in regulated environments.

Affects you ifYou run IBM Granite Speech models locally with llama.cpp; or you are evaluating open-weight speech models for regulated or on-premise deployments.EffortModerate (update to b9768; re-run conversion pipeline for Granite Speech Plus weights; evaluate model quality on your speech tasks).

Benchmarks & Leaderboards

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

  • LMArena: Last model additions were June 17–21 (seed-2.1-pro-preview to Code Arena on June 21, GLM 5.2 Max and Minimax M3 to Agent/Text/Code leaderboards on June 16 — all just outside or at window edge). No June 22–23 additions confirmed. Top 5 overall unchanged: Claude Opus 4.8 (~1510 ELO), GPT-5.5 Pro, Gemini 3.1 Pro Preview, Claude Opus 4.7, GPT-5.5.
  • SWE-bench Verified: Unchanged. Claude Mythos 5 at 95.5% (suspended), Claude Fable 5 at 95.0% (suspended), Claude Opus 4.8 at 88.6%.
  • CyberGym / ExploitGym / SEC-bench Pro: New data from OpenAI Daybreak announcement — GPT-5.5-Cyber 85.6% CyberGym, 39.5% ExploitGym, 69.8% SEC-bench Pro — covered in full in Model Releases.
  • Kimi K2.7 Code: Still no independent third-party results. No Scale SEAL submission, no swebench.com entry, no LiveCodeBench result as of June 23. Watch June 23–26 window.

Technical Discussions

Nothing cleared the quality bar this period. No Hacker News threads with score >200 for AI developer topics identified in the June 22–23 window. Simon Willison's June 22 post (Moebius WebGPU port) is covered in Trends above. No r/MachineLearning or r/LocalLlama threads with sufficient technical depth and recency confirmed.

Quick Hits

  • llama.cpp b9767 (June 23, 08:58 UTC) — WebGPU MTP inference optimization: improves multi-token prediction inference on WebGPU by switching to the mat-vec path for small batches, avoiding unnecessary full matrix multiplication when batch size doesn't warrant it. Relevant if you run llama.cpp WebGPU backend with MTP speculative decoding. [https://github.com/ggml-org/llama.cpp/releases/tag/b9767]
  • llama.cpp b9769 (June 23, 11:43 UTC) — Vulkan debug build fix: links ggml-cpu when GGML_VULKAN_CHECK_RESULTS or RUN_TESTS are enabled, resolving undefined symbol errors in debug builds on Vulkan. Relevant only if you build llama.cpp from source with Vulkan debug flags. [https://github.com/ggml-org/llama.cpp/releases/tag/b9769]
  • llama.cpp b9770 (June 23, 12:25 UTC) — Server remote preset handling fix: corrects behavior when loading remote presets in llama-server configuration; adds test coverage to prevent regression. Relevant if you use llama-server with remote preset configurations. [https://github.com/ggml-org/llama.cpp/releases/tag/b9770]
  • llama.cpp b9771 (June 23, 13:27 UTC) — Vulkan mul_mm ALIGNED as spec constant: refactors the alignment constant in the Vulkan matrix multiplication shader path to a spec constant, reducing the number of compiled shader variants and decreasing binary size. No user-visible behavior change. [https://github.com/ggml-org/llama.cpp/releases/tag/b9771]
  • llama.cpp b9773 (June 23, 15:43 UTC) — Vulkan GET_ROWS_BACK support: adds GET_ROWS_BACK operation to the Vulkan backend, extending the set of ops covered by GPU acceleration on Vulkan. Relevant for workloads that trigger this path on Vulkan hardware (AMD/Intel GPUs). [https://github.com/ggml-org/llama.cpp/releases/tag/b9773]
  • llama.cpp b9774 (June 23, 16:17 UTC) — Vulkan backend test coverage expansion: adds backend tests for SQR, SQRT, SIN, COS, CLAMP, LEAKY_RELU, and NORM ops on Vulkan; testing infrastructure only, no functional changes. [https://github.com/ggml-org/llama.cpp/releases/tag/b9774]
  • llama.cpp b9775 (June 23, 16:48 UTC) — Server draft context creation error check: adds explicit error checking for draft model context initialization in llama-server, converting a silent failure into a detectable error. Relevant if you use speculative decoding via draft models in llama-server. [https://github.com/ggml-org/llama.cpp/releases/tag/b9775]

Worth Watching (Announced, Not Yet Shipped)

12

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

(Countdown updated — was 3 days)

gemini-3.1-flash-image-preview and gemini-3-pro-image-preview shut down June 25. Migrate to stable image model equivalents immediately. 2 days remaining.

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

(Countdown updated — was 5 days)

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 — **Still Pending (Expected June 23–26)**

(Status: no change — still waiting as of June 23)

Weights released June 12, Arena leaderboard entry June 17. As of June 23, no independent third-party SWE-bench Verified, SWE-bench Pro, LiveCodeBench, or GPQA results exist. Vendor-reported: Kimi Code Bench v2 at 62.0 (vs 50.9 for K2.6), but no Scale SEAL submission. Watch swebench.com and livecodebench.github.io.

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

(Countdown updated — was ~23 days)

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

⚠️ 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 23.

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

(Status unchanged)

Both models remain suspended under the US export-control directive issued June 12. LiteLLM v1.90.0-rc.1 added routing entries for Claude Fable 5 as a placeholder — no reinstatement date from Anthropic. 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 (160 days)**

(Countdown updated — was 161 days)

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.