โ† All digests
AI Developer Digest

Thu, Sep 24, 2026

11 signals that cleared the gate52 scanned24 min read
The Signal โ€” start here
Two cost-impacting changes land on the same day: OpenAI's Sora-2 API terminates permanently today (any code calling sora-2, sora-2-pro, or the Videos API is broken right now), and Anthropic expands billing to cover pre-output refusals in the bio, frontier_llm, and reasoning_extraction categories โ€” a change that quietly recalculates the cost floor for any app built on Claude Fable or Opus models. On the tooling side, Cline Desktop reaches Linux today, closing the last major platform gap for the most widely used open-source coding agent harness. And a new benchmark, KEX-bench, puts numbers on something the security community has suspected: frontier coding agents solve 56% of Linux kernel exploit generation tasks without any reference proof-of-concept.
Must-reads today
1
Sora-2 API terminated today โ€” if your app calls sora-2, sora-2-pro, or OpenAI's Videos API endpoint, it is broken right now; migrate to an alternative video generation API
2
Anthropic Expanded Refusal Billing โ€” pre-output refusals in bio, frontier_llm, reasoning_extraction categories now billed at full model rates; update cost projections for Fable/Opus-based apps

๐Ÿ† Repo of the Day

1

akitaonrails/ai-memory โ€” shared agent memory that follows you across tools, machines, and teammates

Docker (recommended for production)

docker run -d --name ai-memory -p 127.0.0.1:49374:49374 \

-v ai-memory-data:/data akitaonrails/ai-memory:latest

Wire up Claude Code (or any supported harness)

ai-memory install-mcp --client claude-code --apply

ai-memory install-hooks --agent claude-code --apply

Ask in the next agent session:

"where did we leave off?"

"search memory for X"


Breaking Changes

1
โ—Breaking

OpenAI Sora-2 API โ€” all endpoints terminated September 24, 2026

What changed
The Sora-2 API (announced for shutdown on March 24, 2026) has reached its termination date. All programmatic access to sora-2, sora-2-pro, and any calls to the Videos API endpoint are no longer functional as of September 24, 2026.
TL;DR
Any app or pipeline that calls sora-2, sora-2-pro, or the OpenAI Videos API endpoint has been broken since today's UTC rollover; OpenAI's consumer-facing Sora app had already shut down April 26, 2026.
Developer signal
(1) Check your dependencies and API call sites now. Search your codebase for sora-2, sora-2-pro, videos.generate, and any calls to https://api.openai.com/v1/video/* โ€” these are all dead endpoints as of today. (2) Migration options for AI video generation: Google's Veo API (via Gemini API โ€” veo-2-0826 and veo-3-0725 are the current stable versions), Runway ML API, and Pika API are the three most commonly cited alternatives. Veo 3 is closest to Sora's creative quality on narrative clips and has Google's API SLA backing it. (3) Sora's research team continues internally (world simulation for robotics), but OpenAI has no public timeline for any new video generation API. (4) If you archived any Sora outputs: the output files from prior calls are unchanged; only new generation requests fail. (5) No credits for unused Sora API prepayment have been announced; contact OpenAI support if you held a balance.


Affects you ifYou built any integration, pipeline, or product feature using the OpenAI Sora or Videos API.EffortSignificant โ€” requires identifying all call sites, switching to an alternative video generation API, updating authentication/endpoint config, re-testing output quality, and updating any cost model or quota tracking.

API & SDK Changes

1
High

Anthropic Expanded Refusal Billing โ€” pre-output refusals in `bio`, `frontier_llm`, `reasoning_extraction` now billed

What changed
Pre-stream refusals in three specific categories (bio, frontier_llm, reasoning_extraction) are now billed at the requested model's standard rates. Before today, any refusal that occurred before any output tokens were returned was not billed. The change applies to all platforms (API, Bedrock, Vertex).
TL;DR
A Claude Fable 5.1 request that returns stop_reason: "refusal" with stop_details.category: "bio" (or "frontier_llm" or "reasoning_extraction") before producing any output now incurs the full input-token cost at the Fable 5.1 rate ($3/MTok).
Developer signal
(1) Audit your app's use cases if they touch life sciences, AI model discussion, or reasoning-extraction patterns. The bio category covers requests related to bioweapons and CBRN materials; frontier_llm covers requests to extract training data, weights, or detailed training procedures from frontier models; reasoning_extraction covers attempts to elicit full internal reasoning chains in ways that circumvent safety measures. If your app serves researchers, enterprise users, or includes open-ended question fields where users could probe these areas, your refusal rate in these categories will now accrue costs. (2) Check your fallback setup. Anthropic's fallbacks: "default" SDK parameter (added in the fable-5-fallback beta) handles refused requests by automatically retrying on a fallback model; with today's billing change, a Fable 5.1 refusal now costs the Fable 5.1 input-token rate before the fallback model's charge is incurred. Review the SDK middleware docs to understand total cost impact. (3) Mid-stream refusals (stop_reason: "refusal" with some output already returned) were already billed before today โ€” no change there. (4) Refusals in all other categories (those with stop_details.category outside these three, or with a null category) remain unbilled before output. (5) For cost model updates, see: https://platform.claude.com/docs/en/build-with-claude/refusals-and-fallback#how-refusals-are-billed


Affects you ifYou build on Claude Fable 5.1, Fable 5, Opus 5.5, or Opus 5 and your app surfaces user-generated queries that could touch biomedical research, AI model internals, or reasoning-extraction patterns.EffortModerate โ€” no code changes required, but cost projections must be updated; if you expose open-ended user query fields, consider pre-filtering or rate-limiting categories likely to trigger these refusals to bound cost exposure.

Research

1
Medium

KEX-bench: Coding Agents Solve 56% of Linux Kernel Exploit Tasks Without Reference Code

What changed
Prior benchmarks for coding agents on security tasks used controlled, synthetic vulnerabilities or relied on agents having access to reference proof-of-concept (PoC) code. KEX-bench introduces the first benchmark using real, published CVEs in production kernels under conditions where agents have no PoC access โ€” forcing agents to reproduce exploit primitives from scratch.
TL;DR
On 45 tasks across 40 Linux and Windows CVEs (kernel address leak, instruction-pointer control, heap read/write, arbitrary address write), the strongest agent configuration solves 56.0% of Linux tasks and 5.0% of Windows tasks without a reference PoC, and 68.9% overall when given a reference PoC โ€” numbers that change what "achievable" means for kernel exploit generation.
Developer signal
(1) The 56% Linux solve rate without reference PoC is the headline. This is the first publicly verified evidence that a frontier coding agent + model combination can, starting from a CVE description alone, generate a working exploit primitive against a real production kernel at majority success rates. For security practitioners building AI-assisted vulnerability research tools: the capability is real, measurable, and benchmarked. (2) Windows is still hard (5%). The gap between Linux (56%) and Windows (5%) on the zero-PoC condition reflects the complexity of Windows kernel internals versus the more publicly documented Linux kernel ABI โ€” a real signal for teams deciding which platform to focus agent-assisted research on. (3) KEX-bench is the eval suite. The benchmark runs tasks in isolated virtual machines with controlled tools and a deterministic verifier โ€” the hardest bar in the current exploit-generation literature. If you're building security research agents, KEX-bench is the standard to beat. (4) Dual-use implications: The same capability that helps security researchers find kernel vulnerabilities can be misused. Responsible disclosure and access controls around these agent configurations are not optional.


Affects you ifYou build AI-assisted vulnerability research tools; you operate kernel or OS-level security tooling where agent-assisted exploit generation is in scope; you need to know what frontier coding agents can actually do in security contexts.EffortModerate to evaluate (KEX-bench VMs required); results are immediately relevant to anyone using coding agents for security research.
arXiv:2609.25591 (Jang J., Lee G., Lee H., Kim K., Kim J., Jung J., Zhang L.) | Date: September 22, 2026 | Link: https://arxiv.org/abs/2609.25591https://arxiv.org/abs/2609.25591

Tooling

2
Medium

Claude Code v2.1.282 โ€” server-side auto mode classifier, session continuation fixes, extended thinking stability

What changed
Focused stability and behavioral release following yesterday's large v2.1.281 security/gateway release. Key additions: server-side auto mode classifier as the new default, maxProseWidth setting, session continuation bug fixes, and extended thinking preservation fixes for slash commands.
TL;DR
Auto mode on direct Anthropic API now defaults to the server-side classifier when telemetry is off; --continue and --resume no longer re-send prior messages in altered form; extended thinking blocks no longer vanish when running /model, /rename, or /artifacts commands mid-session.
Developer signal
(1) Auto mode classifier changed. If you run Claude Code with --api direct and telemetry disabled (the common configuration for enterprise CI), auto mode now uses the server-side classifier by default instead of the client-side classifier. This changes which shell commands are auto-approved. Verify your CI workflows still behave as expected after upgrading โ€” particularly any workflows that rely on auto-approving specific Bash patterns. (2) Session continuation bugs fixed. The --continue and --resume flags were re-sending earlier messages in slightly altered form, which could break prompt cache hits and distort API reasoning. This has been a silent cost-inflation bug for anyone running multi-session agent pipelines: upgrade to fix it. (3) Extended thinking now survives slash commands. Thinking blocks were being silently dropped when you ran /model, /rename, or /artifacts commands while Claude was working. This is now fixed โ€” critical for workflows that switch models mid-session on complex reasoning tasks. (4) maxProseWidth setting: Add "maxProseWidth": 100 to ~/.claude/settings.json to cap Claude's prose output width in wide terminals while keeping tables and code blocks full-width. (5) Skills in anthropic-skills or claude-ai namespaces no longer auto-load unless published as a named plugin โ€” check any custom skills using these namespace prefixes.


Affects you ifYou use Claude Code's --continue/--resume flags in multi-session agent pipelines; you run Claude Code in auto mode with telemetry disabled; you use extended thinking with slash commands; you have custom skills in anthropic-skills or claude-ai namespaces.EffortQuick โ€” claude update or bump your version pin; verify auto mode behavior in CI after upgrading.
Medium

Cline Desktop v0.0.35 + CLI v4.1.21 โ€” Linux desktop app ships; model catalog grows to 6,386

What changed
Cline Desktop v0.0.35 ships .deb and .rpm packages for Linux (x64), completing native desktop coverage across macOS, Windows, and Linux. Simultaneously, CLI v4.1.21 adds the ai& provider (Japanese open-weight models via an OpenAI-compatible endpoint), expands the model catalog to 6,386 models across 209 providers, and sets Claude Opus 5.5 as the default for 11 providers.
TL;DR
Linux developers can now run Cline Desktop natively with .deb/.rpm packages; the model catalog across all three Cline surfaces (Desktop, CLI, IDE extension) now covers 6,386 models, with 11 providers defaulting to Claude Opus 5.5.
Developer signal
(1) Linux Desktop is here. Install via apt install cline-desktop_0.0.35_amd64.deb or the equivalent RPM. This brings plugin slash commands (previously broken in Desktop), provider-specific reasoning-effort memory, and the Diagnostics export feature (Settings โ†’ export a support-safe text file with logs and config) to Linux users. (2) Diagnostics export is worth knowing. When filing a GitHub issue for a Cline Desktop problem, you can now export a single text file with version, OS, settings, logs, and session manifests with sensitive data stripped โ€” substantially faster than manual log collection. (3) Claude Opus 5.5 is now the default for 11 providers. If you use any of the 11 affected providers in Cline and haven't pinned a specific model, you'll be on Opus 5.5 after upgrading โ€” check costs and expected behavior before updating in production workflows. (4) Local model session stability improved. Long Ollama/LM Studio/llama.cpp sessions that previously failed at the model's output-token limit now compact and retry instead of dying โ€” reducing silent session truncation on local model workflows. (5) New ai& provider serves open-weight Japanese language models via an OpenAI-compatible endpoint โ€” the first Japan-focused provider in the Cline catalog.


Affects you ifYou use Cline on Linux; you run Cline with local models (Ollama, LM Studio, llama.cpp) on long sessions; you depend on provider defaults and haven't pinned a model.EffortQuick โ€” update Cline Desktop/CLI; verify provider defaults haven't changed for your workflow.

Rising Dev Tools

1
Notable

akitaonrails/ai-memory โ€” cross-agent memory that survives tool switches, machine changes, and team handoffs

Developer signal
Install via Docker or native binary; wire to any supported agent harness with ai-memory install-mcp --client <harness> --apply. The zero-LLM offline mode (FTS5 full-text search) works out of the box without any API key โ€” add Anthropic/OpenAI keys only if you want semantic ranking. Typed handoffs (ai-memory handoff create) give you a claim-once protocol for parallel agent sessions: agent A creates a handoff, agent B claims it, both sides see the claimed state. For teams: the server supports per-project shared memory with user attribution and audit logs. Note: star-history.com was egress-blocked in this scan โ€” momentum is from GitHub Trending weekly data only; validate the growth curve before treating this as confirmed sustained growth.


Affects you ifYou switch between more than one coding agent harness; you run parallel agent sessions where context overlap matters; you work in a team where multiple people or agents touch the same codebase.
GitHub Trending (all languages, weekly) | Stars: ~8.3k (โ†‘ +1,208 this week) | Link: github.com/akitaonrails/ai-memory

Benchmarks & Leaderboards

SWE-bench Pro (September 2026 update): Claude Opus 5.5 leads the BenchLM SWE-bench Pro table at 89.9%, ahead of Claude Fable 5.1 (81.2%) and Claude Mythos 5 (80.3%), across 75 evaluated models. Separately, on Scale's standardized public/commercial split: Muse Spark 1.1 leads at 61.5% (public) / 51.5% (commercial), with GPT-5.4 xHigh at 59.1% and Claude Opus 4.6 at 47.1%. Sources: benchlm.ai/benchmarks/swe-bench-pro; morphllm.com/swe-bench-pro โ€” September 2026 updates


Technical Discussions

Nothing cleared the quality bar this period. simonwillison.net was egress-blocked. Nathan Lambert, Eugene Yan, and Sebastian Raschka had no Sep 24 posts confirmed. No HN threads with score >200 and new Sep 24 technical depth confirmed.


Quick Hits

  • pydantic-ai v2.49.0 (Sep 24) โ€” Adds GitHubCopilotOAuthFlow device authorization, BoolCriteria for boolean fields, TypeSafeModel whole-number choices; fixes streamed OpenAI logprobs, GPT models on Bedrock, Gemini Live audio. [github.com/pydantic/pydantic-ai/releases/tag/v2.49.0]

Worth Watching (Announced, Not Yet Shipped)

3

Claude Sonnet 5.5 and Haiku 5.5 โ€” within weeks

Anthropic confirmed both follow Opus 5.5 "within weeks" of the September 22 release. No pricing or specific dates announced. [anthropic.com/claude-opus-5-5]

Google Antigravity `antigravity-preview-05-2026` shutdown โ€” **October 5, 2026 (11 days)**

Migrate to antigravity-preview-09-2026, rename snake_case built-in tool parameters to PascalCase, and update file-edit handling. See September 18 digest Breaking Changes for the full migration guide. [ai.google.dev/gemini-api/docs/changelog]

GPT-6 Astra billing starts October 5, 2026 (11 days)

Standard pricing: $10/$1 (cached)/$50 per MTok. Long context (>272K tokens): $20/$75 per request. Free billing period ends October 4. [platform.openai.com/docs/changelog]



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