A long-context request returned another tenant’s data after every smoke test passed.
Upgrade SGLang and add a cross-tenant rejection-path test before the next model rollout.
Understand the changes. Choose the tools. Put AI to work.
NO FEED / News
What changed in AI development, and why it matters.
188 news items
Upgrade SGLang and add a cross-tenant rejection-path test before the next model rollout.
TypeScript agent loops that need actionable failure and version telemetry.
Claude Code users with long sessions, large instruction files, or slow MCP servers.
Teams deciding how much command and file approval to automate.
AI SDK 7 users with tools, approvals, provider streams or exhaustive finish-reason handling.
Claude Code users relying on sandboxing, deny rules, MCP policy or unattended sessions.
LangChain applications that parse raw streamed tool-call events.
Python applications using Decisions or Live response models.
Pilot one high-volume bounded decision against labeled production examples.
Claude Code users running remote MCP tools with side effects.
Pilot expiring credentials after removing every cached-token dependency.
Python applications using WebSocket calls, browser tooling, or the recording example.
Inspect session-level routing and cache reuse before increasing the model budget.
Computer-use agents and benchmarks still targeting Cua Cloud.
Agents driving mobile tests through Mobile MCP.
SGLang operators combining hybrid models, speculation and constrained output.
Applications already using OpenTelemetry.
Maintainers of organization and workspace administration scripts.
Teams resuming interrupted sessions or reconciling gateway spend.
Move affected sessions to 2.1.291 and verify approval delivery plus quit/resume behavior.
Managed Claude Code environments and owners of subagent configurations.
Teams using natural-language hooks as gates or completion checks.
Upgrade, then check the plugin write boundary and the headless stop condition.
Owners of policy hooks and unattended sessions with remote MCP servers.
Try an observable, bounded mod; test every behavior-changing hook before team rollout.
Teams accepting unattended workflow results.
Codex CLI users relying on Linux filesystem restrictions.
Codex users with resumed tasks or managed network rules.
Move affected Copilot workflows before 16 November; check annual-plan eligibility separately.
Pair a machine for remote steering; make its power and connectivity requirements part of the task plan.
Keep the current plan until the model-level budget and permanent account changes are clear.
Copilot users choosing a model for complex coding tasks.
Evaluate one narrow subagent role and measure completed-task cost on both sides of 100K.
Test timeout, partial-output and empty-stream cases through your client before rollout.
Harness builders routing requests or screening candidate tool calls.
OpenRig operators relying on the previous network default.
Orca users running GitHub Copilot on shared machines or SSH hosts.
Pi users with terminal preferences or multiple MCP identities.
Pi scripts that use tool filtering as an execution boundary.
Pi extension authors using session-start hooks and triggered custom messages.
Inbox users answering several agent questions from a phone.
Try it on one supported session; verify stale-plan rejection and resumed decision delivery.
Pi users keeping Plannotator reviews open across session changes.
Developers coordinating several agent sessions that need human decisions.
Pydantic AI v2 applications using model concurrency limiters and streaming.
Pydantic AI applications using BrowserUse.
Compare accepted-task time and cost on a fixed workload; change the default only after that comparison.
Find the pinned model calls now; finish and verify the migration before 30 November.
Teams whose parallel agents reset or migrate a local database.
Test managed-policy routing before rolling 1.142 across a team.
Teams whose scripts or onboarding docs call plugin-creator, or who pin Codex config files. Check before upgrading.
Run it against your own task set before you move traffic. The price is verified; the capability claims are OpenAI's own runs.
Anyone whose pydantic-ai agents fetch pages they do not control. Upgrade either line today.
Nothing fails until you switch models. Before switching, search your code for "disabled" thinking and forced toolchoice, and test any flow that moves a conversation between accounts.
Teams that run coding agents or CI on self-hosted runners with pinned images. Check runner versions this morning; the new runner-deprecation REST API returns the cut-off dates for each version.
Anyone running MCP clients against servers with long tool lists, or keeping OAuth tokens in a strict schema.
Nothing fails today. Replace litellm-proxy with lite in scripts, Dockerfiles and CI now, and check any job that treats stderr output as a failure.
Anyone running worktrunk to manage agent worktrees with commit hooks that read the current branch, or scripts that parse its hook logs.
Teams that collect Claude Code usage through OpenTelemetry configured per repository.
Pick a default this week, and set MCP servers and Code Review explicitly so neither depends on the global setting.
Do not rely on native AGENTS.md loading yet. Put a one-line CLAUDE.md containing @AGENTS.md next to it; @ imports do not depend on the flag.
Anyone pinning an old third-party action by SHA, or running self-hosted runners on older Macs or ARM32 boards.
Teams letting an agent run shell commands against a working tree that also holds credentials.
Worth moving to, but read the migration notes before you change the model string. The three 400s are the whole of the work, and each has a named replacement.
Anyone whose CI, deploy keys or agent sandboxes speak Git over SSH from a pinned or old client image.
Anyone running a long-lived agent loop on GPT-6 whose input bill is mostly re-sent context.
Anyone with a Sol or Luna line in a production bill, and anyone who priced an agent out at the old rate.
Anyone running the Cline CLI on Windows, and anyone who has delegated work to configured subagents.
Copilot Business and Enterprise admins, whose default-enablement policy turns new models on unless they opted out.
Read the upgrade notes before this reaches a pinned deployment. The removals are recoverable; the YaRN context-length change can surface as user-visible request failures instead of a startup error.
go install the CLI and read the concepts doc if the density argument interests you. Nothing here survives a migration plan yet.
Anyone who has wt switch --no-cd -x inside an alias, a hook or a script.
Every repository whose CI says ubuntu-latest — which is most of them.
Anyone pointing Cline at minified bundles, binaries or screenshots and watching long tasks die quietly.
Anyone who wants an agent's file writes and shell to happen on a dev box rather than a laptop.
On Claude Code 2.1.275 behind a gateway, or Cline desktop 0.0.31: you are broken, and the fix is published. Upgrade both.
The design and the raw chart data are public and worth an hour. They will not settle a harness migration on thirty tasks — price your own rollouts before you move.
Anyone running pydantic-ai agents with webfetch enabled, or shipping OTel spans off-box.
worktrunk users with hook scripts or --execute templates checked into a shared repo.
If you have been stitching a cascaded stack out of a recogniser, a model and a voice, this collapses three hops into one, with Live API integrations through LiveKit, Pipecat and Vercel. Enterprise access is still private preview.
Anyone whose pipeline still builds on an old base image. A TLS stack that only offers SHA-1 signature algorithms can no longer reach github.com, and it surfaces as a handshake failure in a clone that worked on Monday. Audit the oldest image in your CI first.
Join the waitlist and keep the pricing table. Hold the verdict until somebody outside the company has run it on their own workload.
Anyone running Claude Code under an organisation policy, or installing plugins from a script
Upgrade. On a large workspace, or on a provider that forwards 429s, this removes two failure modes you may have been blaming on your own machine.
Anyone compiling against libllama, and anyone serving Qwen, Kimi or GLM locally
Anyone already running the Cline desktop app, especially on OpenCode Go models or Cline Pass
Nothing to install beyond Cline desktop 0.0.27. Re-run any GitHub-dependent job that failed between 09:16 and 10:45 UTC on Sunday before you spend time debugging it.
Teams on google/adk-python with workflows, GCS tools, or MCP servers
Anyone on Claude Code latest/next — mandatory if ANTHROPICBASEURL or a third-party compatible endpoint is in the path
Claude Code: pin ≥2.1.268, especially on ANTHROPICBASEURL / third-party gateways. ADK operators: read 2.9.0 before upgrade — make node bodies idempotent and set localfileroot. Expect MAI-Code-1-Flash gone from Copilot.
Anyone on Claude Code latest/next — especially gateway, Bedrock/Vertex, or long resume sessions
Codex users who want Astra: ≥0.154.0. Claude Code: pin ≥2.1.267. Expect MAI-Code-1-Flash gone from Copilot. Copilot Business/Enterprise admins: review agent permission policies.
Anyone on Codex CLI/TUI who wants Astra or isolated session checkouts
GitHub Copilot Business/Enterprise admins rolling out agent workflows
Anyone on Claude Code with a gateway, proxy, or non-default auth path — and anyone who landed on 2.1.265 overnight
Pin Claude Code ≥2.1.266. If you took 2.1.265 on a gateway/proxy path, upgrade today. MAI-Code-1-Flash leaves Copilot tomorrow (10 Sep).
Anyone hosting or calling MCP over HTTP with the official Python SDK
Read 2.2.0 before upgrading MCP Python 2.x — redirects, idle sessions, and OAuth issuer checks change defaults. 1.x operators: ≥1.30.0. MAI-Code-1-Flash leaves Copilot 10 Sep.
No new decision pin inside the window. If you track npm latest, 2.1.263 is the tag; stable remains 2.1.236. MAI-Code-1-Flash leaves Copilot 10 Sep.
Anyone on Fable 5.1 in Claude Code after 2.1.257–259
Pin Claude Code ≥2.1.260 if you run Fable 5.1. On Copilot, enable Gemini 3.8 Flash and plan the 2 Oct model cutover.
Cline Desktop users and anyone with both desktop and CLI installed
Copilot Pro through Enterprise pinning Gemini Flash, Kimi, or Opus 4.7
Org Claude Code fleets and unattended hosts
Codex CLI/desktop on 0.152.x
Pin Codex ≥0.153.0 over 0.152.x. Claude Code latest 2.1.259 for multi-session and headless; stable only if you need the slow channel.
Copilot Business/Enterprise admins shipping agentic app/CLI
Mac 12 hosts and anyone on remote/scheduled Claude Code
Long-running agent work on Claude Code, API, or Copilot
Pin Claude Code ≥2.1.258. Try Fable 5.1 for long agent runs; on Copilot, read the retention policy before enabling org-wide.
Cline extension/desktop on long tasks or unpinned Anthropic models
Mac CLI and Remote Control hosts on latest
Codex CLI/desktop on 0.151 or a 0.152 alpha
Pin Codex ≥0.152.0. Claude Code latest 2.1.252 for Mac/Remote Control fixes; stable only if you need the slow channel.
No pin from today. Plan Cursor OpenAI traffic through 12 Nov; re-budget Claude Code weekly after 14 Sept.
orgs rotating API keys and anyone still on files-api / skills beta headers
anyone running Claude Code in CI, shared machines, or multi-hour sessions
latest ≥2.1.248 for --restricted and the hourly cache fix; pin stable only if you need the slower channel.
terminal Codex users and teams wiring interrupt-time automation
anyone running vLLM servers or pinning CUDA/ROCm serving images
vLLM: checklist bnb plugin + Transformers ≥5.15 before upgrade. Claude Code: latest ≥2.1.247 for those fixes; stable remains 2.1.231.
Plus Codex/Work: plan around a 5h rolling window again, or move Pro / credits / another harness. Claude Code on Bedrock or a gateway: stay on latest ≥2.1.239 (ideally 2.1.246); stable still lacks those fixes.
anyone on latest/native Claude Code, MCP servers, or ANTHROPICBASEURL gateways
local llama.cpp / server / multimodal runners, especially DeepSeek 4 multi-GPU
If you already call Sol (or gpt-5.6), re-check invoices and budget alerts against $4/$20. Prefer Batch or Flex for offline work. Pin gpt-5.6-sol if you need the promo rate to stay attached to a snapshot name.
anyone shipping MCP servers or clients on the Python SDK
On Bedrock or a gateway: install ≥2.1.239 (or set minimumVersion 2.1.239 on stable). Confirm with claude --version. Others can wait for stable.
Cline users with MCP tools or who need the new catalog rows
Pin anthropic>=1.0.0 only after you clear MIGRATION.md. If you construct HTTP clients or mock httpx, switch imports to httpx2 first. Drop any remaining Completions callers. Python <3.10 stays on 0.125.x.
Codex multi-session operators and SDK embedders
anyone on pydantic-ai with Anthropic models and unpinned anthropic
Pin anthropic ≥0.124.0, drop both beta headers on new code, and set file expiry on upload. Keep the beta header only if a client still parses the pre-GA list shape.
Claude Code daily drivers on multi-session hosts, gateway proxies, and anyone drowning in preamble
OpenAI Agents SDK users with guardrails, multi-checkpoint runs, or explicit client wiring
Turn it on for Pro/Max/Team if you want cross-device handoff. Keep auto-approve off for mail and Drive until you have tried a throwaway folder. Enterprise: confirm the admin toggle before assuming the rollout reached you.
Codex CLI/TUI users on multi-hour sessions, Bedrock shops, and anyone metering agent spend
teams that must pin OpenAI calls to a residency region from Python
Claude Code daily drivers on Pro/Max/Team and multi-session hosts
Treat Origin as a research preview: try on a throwaway org if you want agent-side repo UX, keep production source of truth on GitHub until data terms and agent-native merge features land. Enterprise admins who never decided on a second host should confirm the opt-out posture.
teams calling OpenAI-format APIs through Bedrock Runtime
pydantic-ai agents on Bedrock or Gemini with strict schemas
harness authors comparing open runtimes to Claude Code / Codex
Meter DeepSeek by UTC hour. Prefer off-peak for batch and long loops; pin Pro-0813 or Flash-0731 so a silent version cell cannot surprise you.
OpenAI Agents SDK users who need hard call budgets or tighter sandboxes
If you never set a default, decide before the next session: keep auto and pin ask rules on git push / gh pr create, or set "defaultMode": "manual" in ~/.claude/settings.json. Org admins who want the old baseline set permissions.disableAutoMode to disable.
anyone metering DeepSeek as a default agent model
Copilot orgs picking a cheap coding model this week
ADK agents that pair output schemas with tools, or return media from tools
anyone who runs the pydantic-ai dev web chat on a workstation
plugin authors and Copilot org admins
auto-mode users without attribution headers; plugin authors
Cline users on Claude Code or desktop
Pin Pro 0813 and run one trusted agent loop; budget for a price change with no date. Try Grok 4.6 on one long job this week under the 2× promo; keep Composer for cheap daily edits.
goose hosts metering multi-turn runs
Copilot teams on MAI-Code-1-Flash or picking a cheap coding model this month
JetBrains users who want local models or cross-session memory without leaving the IDE
local-agent hosts already on Ollama who want a small-active MoE next to Glimmer
anyone who constructs a custom httpx client for the OpenAI SDK
anyone who runs the pydantic-ai dev web chat on a workstation
real product on paid tiers. Try one end-to-end job on your own tools before you trust the seat. Skip if you are not already on Ultra or Heavy.
anyone whose agents default to Sonnet 5 and who had a 50% step-up in the September forecast
Cline users who thought Yolo did something, and anyone on Vertex
weights and HF load path are real; treat consumer-GPU speed claims as vendor until you time a tool loop on your box. Pin a digest, run one agent scaffold you already trust, measure tokens/sec and tool-call success before you move anything off the cloud default.
anyone who depended on the previous default model without setting one
anyone spinning agent sandboxes on Vercel who was baking tools at boot
self-hosters pinning a serving engine this week, especially Kimi K3 or DeepSeek-V4 traffic
anyone metering usage behind an OpenAI-compatible proxy serving reasoning models
already on auto mode — only the free classifier is new. On manual or YOLO, decide before the 14th: Shift+Tab still flips modes; admins can pin or disable auto. Do not read 89% as solved; eleven percent still gets through.
teams whose code cannot leave their own hardware, and anyone who wanted a plugin they could verify by hash
anyone standardising on Codex who has been hand-copying skills between tools
the format is one day old and one client ships it. If you maintain plugins for two agents, read the spec now — the directory shape is cheap to adopt and costs nothing if it wins. Do not rewrite your distribution around it yet.
anyone about to move a team's default model on the strength of a benchmark table
anyone whose agent carries forty tools and pays for the list on every single call
anyone running classification or extraction over a large corpus
anyone administering Claude Code across a company rather than a laptop
teams where two people wrote a slash command with the same name
anyone pinning the Gemini CLI in CI
it is beta, it needs a login, and the announcement publishes no price. Meta says Spark 1.2 has "expanded global access" — which is not the same as saying where. Steal the event-log design; wait on the harness.
anyone driving an agent over SSH or in CI
do not treat this as a product recall. Treat it as a reason to keep approval gates and network egress on any agent that can open PRs or message people, including the ones you already trust.
anyone running Claude Code with worktrees, subagents, or auto-mode on a shared repo
teams already on Kiro who want unattended multi-session work
teams standardising on one editor extension
the verbosity objection resolves in its favour. It emits 210M tokens on the index run against a median of 100M, and still costs $0.03 per task where GPT-5.6 Sol costs $1.86. Nine index points, sixty times the money.
CI jobs that stall rather than fail
anyone with a high-volume batch job costed at last week's prices
anyone who abandoned MCP for shell tools last year
anyone who tried to make one assistant serve a whole company