← All digests
AI Developer Digest

Tue, Sep 29, 2026

15 signals that cleared the gate35 scanned25 min read
The Signal — start here
OpenAI DevDay 2026 was the biggest single-day developer announcement event in OpenAI's history — 20+ products, three of which land immediately on developer desks: GPT-6.1 Sol (near-Astra performance, ~$2/$10 per MTok, one-fifth the per-task cost of Astra on coding evals), the Agents API public beta (managed runtime with computer use, MCP server connections, parallel subagents, and durable session state), and the Decisions API limited preview (low-cost GPT-6 Luna for structured classification and routing). Both Claude Code (v2.1.285) and OpenAI Codex (rust-v0.159.0) also shipped independently today — the weekly simultaneous release cadence from both camps is now a pattern, not a coincidence. The dominant infrastructure story underneath DevDay: both OpenAI and Anthropic are now actively competing for the orchestration layer above the model, not just the model itself.
Must-reads today
1
GPT-6.1 Sol — near-Astra on DeepSWE v1.1 and AutomationBench at $2/$10 per MTok; if you're evaluating OpenAI models for coding agents, benchmark this immediately
2
OpenAI Agents API public beta — managed agent runtime with hosted computer use and MCP is now available; the orchestration infrastructure you had to build yourself is now a service
3
Claude Code v2.1.285 — fixes a credential-exposure bug (/ultrareview uploading uncommitted credential files) and a token-limit bug (model switching mid-session); update now

🏆 Repo of the Day

1

dzhng/jevgrep — find code by asking what it does, not what it's named

npm install -g jevgrep

Ask what code does instead of what it's named:

jevgrep "retry logic for API calls"

For coding agents — pipe directly into context:

jevgrep "authentication middleware" | head -100


Breaking Changes

1
●Breaking

OpenAI Agent Builder shut down November 30, 2026 — migrate to AgentKit

What changed
Agent Builder (the drag-and-drop agent canvas launched at DevDay October 2025) is being deprecated with a hard shutdown date of November 30, 2026. All agents built in Agent Builder must be rebuilt in AgentKit (the Agents SDK + Responses API bundle) before that date.
TL;DR
Agent Builder shuts down November 30, 2026; any agent built there stops working on that date — migrate to AgentKit (Agents SDK + Responses API), which was announced today alongside the Agents API public beta.
Developer signal
Agent Builder was a no-code/low-code canvas for building GPT-powered agents. If your team used it to prototype or deploy agents, you have ~63 days to rebuild. The replacement is AgentKit, which bundles the Agents SDK, Responses API, and the new Agents API public beta. Concretely: pull the configuration from your Agent Builder agents (the system prompt, connected tools, and data sources), move them into the Agents SDK, and validate that behavior is equivalent. The Agents API public beta now supports hosted execution so feature parity is achievable. OpenAI has not published a migration guide as of this digest; watch platform.openai.com/docs/changelog.


Affects you ifYou built or deployed agents using OpenAI's Agent Builder canvas.EffortSignificant — requires rebuilding agent configurations in code using the Agents SDK.
OpenAI DevDay 2026 / Platform Docs | Date: September 29, 2026 | Link: https://openai.com/index/devday-2026-recap/https://openai.com/index/devday-2026-recap/

Model Releases

1
High

GPT-6.1 Sol — near-Astra coding performance at $2/$10 per MTok

What changed
GPT-6.1 Sol replaces GPT-6 Sol as OpenAI's efficiency-tier frontier model; on DeepSWE v1.1 it matches GPT-6 Astra at roughly one-fifth of Astra's per-task cost, and beats GPT-5.6 Sol's best score by 6.4 percentage points on the same benchmark.
TL;DR
GPT-6.1 Sol scores within ~2 points of GPT-6 Astra on DeepSWE v1.1, OSWorld 2.0, and AutomationBench at $2/$10 per MTok (cached input $0.10/MTok) — one-fifth of Astra's per-task cost on coding evals.
Developer signal
The benchmark story is unusually strong for an efficiency-tier model. On the four benchmarks OpenAI published — DeepSWE v1.1 (real GitHub issue resolution), AutomationBench (multi-step business workflows), OSWorld 2.0 (computer use), and Terminal-Bench Science 0.1 — GPT-6.1 Sol "nearly matches Astra" across all four. Specifically: OSWorld 2.0, it comes within 2.1 points of Astra at roughly a seventh of the cost per task; AutomationBench, it scores 2.2 points above Claude Opus 5.5 at about a third of the cost. If you're currently using GPT-6 Astra or GPT-6 Sol for coding-agent workloads, this is worth an immediate benchmark run. Pricing: $2/$10 per MTok standard, $0.10/MTok cached input. Currently available in ChatGPT Work and Codex (Plus, Pro, Business, Enterprise, Edu); API availability for general accounts was not confirmed as of this digest — check platform.openai.com.

| Benchmark | GPT-6.1 Sol | GPT-6 Astra | GPT-5.6 Sol | Claude Opus 5.5 |

|---|---|---|---|---|

| DeepSWE v1.1 | matches Astra | — | −6.4 pts vs Sol 6.1 | — |

| AutomationBench | — | — | — | Sol 6.1 +2.2 pts |

| OSWorld 2.0 | within 2.1 pts of Astra | — | — | — |


Affects you ifYou use GPT-6 Astra or GPT-6 Sol for coding agents or agentic workflows — especially if cost is a constraint.EffortModerate — benchmark against your workload before swapping model IDs; behavior will differ from GPT-6 Sol.

API & SDK Changes

3
High

OpenAI Agents API — public beta with managed runtime, hosted computer use, MCP, and parallel subagents

What changed
The Agents API graduates to public beta. Previously, developers had to build orchestration (sessions, context compaction, recovery) manually on top of the Responses API. The Agents API abstracts that infrastructure: OpenAI handles session lifecycle, orchestration, context compaction, and recovery; developers define tools and environments and get access to a hosted browser (computer use), MCP server connections, and parallel subagent dispatch.
TL;DR
OpenAI's Agents API public beta delivers a fully managed agent runtime — sessions, context compaction, computer use via hosted browser, MCP server connections, parallel subagents, and durable session state — so you supply tools and logic, not infrastructure.
Developer signal
This is the most significant developer-facing announcement from DevDay. Previously building an agent loop on OpenAI required you to manage sessions, handle context compaction manually, provision a browser environment for computer use, and write your own recovery logic. The Agents API public beta removes all of that: you declare tools, connect MCP servers, and spin up parallel subagents via the API; OpenAI's infrastructure handles the rest. Concretely: computer use now requires no separate browser provisioning (use the hosted browser via the API); MCP servers connect directly without a proxy layer; parallel subagents are a first-class primitive rather than a pattern you implement yourself. For teams currently running agent workloads on the Responses API with manual orchestration: this is worth evaluating for workloads where operational overhead (session recovery, compaction) is a pain point. The Agents API also underpins the new Codex multi-agent capabilities. AgentKit (Agents SDK + Responses API + Agents API) is the full bundle.


Affects you ifYou build multi-step agent pipelines on OpenAI's API; you currently provision your own browser environment for computer use; you manually manage context compaction or session recovery in agent loops.EffortModerate — new API surface, migration from manual Responses API orchestration requires architectural review.
OpenAI DevDay 2026 | Date: September 29, 2026 | Link: https://openai.com/index/devday-2026-recap/https://openai.com/index/devday-2026-recap/ (full docs at developers.openai.com)
Medium

OpenAI Decisions API — limited preview: structured classification and routing with GPT-6 Luna

What changed
New specialized API for structured decision-making: developers supply a question with a finite set of predefined answers plus context (text or images), and get a structured answer back. Uses GPT-6 Luna (low-cost model). Available in limited preview today; broad release in "coming days."
TL;DR
The Decisions API lets you define a question with predefined answers (e.g., "classify this support ticket: [billing, technical, general]") and get a structured response via GPT-6 Luna — eliminating the overhead of writing classification prompts and parsing free-text output.
Developer signal
For developers who are already using frontier models to classify input, route requests, or decide an agent's next action: the Decisions API gives you a cheaper, more constrained alternative for those decisions. Instead of crafting a system prompt, adding output-format instructions, and parsing the response, you define the question and valid answers declaratively and get a structured answer directly. GPT-6 Luna is OpenAI's low-cost model, so this is priced below standard API calls. Practical use cases: content moderation routing, customer support tier classification, agent next-action selection, and any step in an agent loop where the decision has a finite option set. This pairs well with the Agents API public beta as a cheap routing layer before dispatching to a heavier model. Currently limited preview; watch platform.openai.com/docs/changelog for the broad release.


Affects you ifYou write classification or routing logic using LLM calls with structured output parsing; you build agent routing layers.EffortQuick for new pipelines (declarative API); Moderate if migrating existing classification logic.
Medium

OpenAI Ultrafast — 6× faster API tier, 6× standard pricing (in API and Codex today)

What changed
New premium speed tier for the OpenAI API and Codex: 6× faster token generation in the API, 8× faster in Codex. Opt-in; priced at 6× the standard rate. Available now.
TL;DR
Ultrafast generates tokens at 6× the standard API speed (8× in Codex) at 6× the price: for GPT-6.1 Sol that's $12/$60 per MTok; for GPT-6 Astra it's $30/$150 per MTok.
Developer signal
Ultrafast is the first formal "premium latency" tier in a major LLM API — previously speed was a function of model choice, not an API configuration. For most batch workloads, the cost-to-benefit ratio is poor (6× price for 6× speed, net cost per token unchanged). The cases where Ultrafast changes the calculus: (1) interactive coding-agent workflows where the human is watching and waiting — if task time drops from 30s to 5s, the experience change is significant and the absolute cost is still low per session; (2) real-time streaming in latency-sensitive product UX; (3) Codex in particular gets 8× speed, which at $12/$60 per MTok for Sol 6.1 is still cost-effective for burst-heavy workloads. To access Ultrafast, pass the ultrafast: true parameter in the API (exact parameter name to be confirmed in platform docs). GPT-6.1 Sol Ultrafast is "coming in the coming days" per OpenAI's announcement — only GPT-6 Astra Ultrafast was confirmed as available now in the API.


Affects you ifYou build latency-sensitive agent pipelines; you use Codex for real-time developer-facing features; you're optimizing time-to-first-token or total response time in user-facing products.EffortQuick — opt-in parameter; pricing change is the main consideration.
OpenAI DevDay 2026 | Date: September 29, 2026 | Link: https://openai.com/index/devday-2026-recap/https://openai.com/index/devday-2026-recap/

Research

Nothing cleared the quality bar this period. arXiv.org is egress-blocked — cs.AI, cs.CL, and cs.LG new submissions for September 29 could not be directly fetched and scored. The closest candidate, arXiv:2609.31587 ("Compact Documentation for Coding Agents: A Benchmark, an Optimizer, and Why It Does Not Transfer"), has a strong result (compact documentation does not help agents resolve real repo issues when source is present) but was published September 25 — outside the 24-hour scan window. Moved to near-misses.


Tooling

1
Notable

Claude Code v2.1.285 — credential exposure fix, plugin configure, CLAUDE_CODE_DISABLE_WEB_FETCH

What changed
Four new developer controls (env var to disable WebFetch, desktop app launcher, plugin option configuration, allowedProviders managed setting); two security fixes (/ultrareview was uploading uncommitted credential files, URL passwords with @ characters were exposed in redacted logs); one correctness fix (model-switching mid-session left incorrect output-token limits).
TL;DR
v2.1.285 ships CLAUDE_CODE_DISABLE_WEB_FETCH, claude --desktop, claude plugin configure, and allowedProviders; fixes a security bug where /ultrareview uploads could include uncommitted credential files, and a log redaction bug exposing URL passwords.
Developer signal
Three things worth acting on immediately: (1) Security — /ultrareview credential exposure: if you use /ultrareview and have uncommitted .env, credential, or secret files in your working directory, those files could have been included in review uploads before this fix. Audit any /ultrareview runs you've done with sensitive files present. Update to v2.1.285 immediately. (2) Security — URL password redaction bug: if your MCP server configs or worktree remotes use URLs with passwords (format: user:password@host), those passwords were being logged in redacted logs. This is fixed in v2.1.285. (3) New allowedProviders managed setting: gateway deployments can now restrict which API providers Claude Code is allowed to call — useful for organizations that need to enforce Claude-only usage or specific provider allowlists. Also: CLAUDE_CODE_DISABLE_WEB_FETCH=1 disables the WebFetch tool globally (useful for air-gapped or restricted environments); claude --desktop opens the Claude desktop app on the current directory.


Affects you ifYou use /ultrareview in repositories containing sensitive files (update immediately); you run Claude Code with URL-password-formatted MCP configs; you administer gateway deployments and need provider restriction.EffortQuick — Claude Code auto-updates; audit prior /ultrareview runs for credential exposure.

Rising Dev Tools

2
Notable

dzhng/jevgrep — semantic code discovery CLI for coding agents

Developer signal
Install globally (npm install -g jevgrep), then use jevgrep "retry logic for API calls" — it queries Jev's relevance model across your directory structure and returns file paths plus verbatim excerpts. The key integration: it outputs to stdout as clean file paths + excerpts, making it directly usable as a shell tool in Claude Code (--allowedTools bash), Codex, Aider, or any coding agent that can execute shell commands. The tool calls Jev (TypeSafe's decision model) for relevance scoring — this is not fully local, so requires a Jev account.


Affects you ifYou maintain large or unfamiliar codebases and use coding agents; you build agent workflows that need reliable file discovery as a tool step.
GitHub Trending (TypeScript, daily) | Stars: ~1,670 (↑ trending today) | Link: github.com/dzhng/jevgrep
Notable

mikehasa/golive-skill — agent skill + CLI to deploy agent-built products on your own infrastructure

Developer signal
Install as a global CLI (npm install -g golive-skill) or add as an MCP skill to Claude Code. The workflow: golive detect scans the project and identifies what it needs, golive plan proposes the infrastructure, golive approve lets you review before anything is created, golive apply provisions it on your accounts, golive verify confirms everything is running. The explicit approve step means no resources are created without review. Works with Claude Code, Codex, Cursor, and any agent that can execute shell commands or call MCP tools.


Affects you ifYou use coding agents to build web apps and currently hand-deploy the results; you want a zero-dependency, no-telemetry deployment skill for your agent setup.
GitHub Trending (TypeScript, daily) | Stars: ~1,092 (↑ trending today) | Link: github.com/mikehasa/golive-skill

Benchmarks & Leaderboards

No confirmed new leaderboard entries within the 24-hour scan window. Current SWE-bench Pro standings (as of September 28–29, 2026): Claude Opus 5.5 leads at 89.9%, followed by Claude Sonnet 5.5 (81.3%) and Claude Fable 5.1 (81.2%). On SWE-bench Verified, Claude Fable 5 leads at 0.950 (116 evaluated models). Notable prior entry: Qwen3.8 Max at 67.7% SWE-bench Pro ($2/$6 per MTok) ahead of GPT-5.6 Sol (64.6%) — model released August 3, 2026; leaderboard position confirmed this week but entry predates scan window. lmarena.ai egress-blocked; ELO movements not confirmed for September 29.


Technical Discussions

Nothing cleared the quality bar this period (concrete data, primary source, within window). HN threads on DevDay announcements were accumulating at time of scan but not yet at score >200. simonwillison.net egress-blocked.


Quick Hits

  • OpenAI Codex rust-v0.159.0 — instant_interrupt — New opt-in feature lets users steer Codex mid-response or mid-code-mode by sending an interrupt signal; redesigned welcome screen; expanded Mermaid rendering. Published today. github.com/openai/codex/releases
  • Cline SDK v0.0.87 — Fixed reasoning tokens counted twice in token counter; Bedrock support for OpenAI GPT models through inference profiles; PHP file support added; cloud export gains shared handoff and persistent workspaces. 6,386→6,447 models in catalog. Published today. github.com/cline/cline/releases
  • Grok 4.7 on Amazon Bedrock — Available now as us.xai.grok-4.7 (and global.xai.grok-4.7); 500K token context window; 4 configurable reasoning effort levels; supports Converse, Responses, Chat Completions, and InvokeModel APIs. Announced September 28. aws.amazon.com/blogs/machine-learning/grok-4-7-is-now-available-on-amazon-bedrock/
  • Anthropic service disruption (resolved) — Elevated error rates across claude.ai, Claude Code, Cowork, and the Claude API from 00:50 UTC to 02:10 UTC on September 29. Resolved at 02:35 UTC. No developer action required; monitor status.anthropic.com for future incidents.

Worth Watching (Announced, Not Yet Shipped)

5

GPT-6.1 Sol Ultrafast — "coming days"

Standard GPT-6.1 Sol is available now; the Ultrafast variant (8× speed, 6× price) was announced today but is not yet accessible in the API. Watch platform.openai.com/docs/changelog for the release. [openai.com/index/devday-2026-recap/]

Claude Haiku 5.5 — "coming weeks" (announced Sept 22)

Announced alongside Opus 5.5 on September 22 as "coming in the coming weeks." No model card, pricing, or date announced as of September 29. [Anthropic Opus 5.5 announcement, September 22, 2026]

OpenAI Decisions API — broad release "coming days"

Limited preview today; broad release expected shortly. [openai.com/index/devday-2026-recap/]

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

Standard pricing begins; free billing period ends October 4. [platform.openai.com/docs/changelog]

Google Antigravity `antigravity-preview-05-2026` shutdown — **October 5, 2026 (6 days)**

Migrate to antigravity-preview-09-2026, rename snake_case tool parameters to PascalCase. [ai.google.dev/gemini-api/docs/changelog]



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