Skip to content
NO FEED

Understand the changes. Choose the tools. Put AI to work.

No. 036 · 22 September 2026 · 3 min← No. 035 · No. 037 →
SIGNALNOTABLE|SHIPPED 2|SKIPPED 6

The one thing

01

vLLM 0.30.0 deletes four things you may be running and shortens two model context windows without asking.

vLLM shipped v0.30.0 at 05:20 UTC, 762 commits from 315 contributors, and it is a stable release rather than a candidate.1 The upgrade notes carry removals, and two of them change behaviour silently rather than erroring.

The quiet one is YaRN. vLLM aligned its aliases with Transformers and stopped multiplying max_position_embeddings by the scaling factor twice, so derived max_model_len drops for some models: the notes name TeleChat3-36B-Thinking going from 131072 to 32768, and sarvam-105b from 5242880 to 131072.1 A serving stack that relied on the old arithmetic will start refusing long requests it accepted yesterday, with no deprecation warning in between.

VERDICT · BREAKING — 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.
The full removal list, and what 0.30.0 gives you in exchange

GPTQ group and dynamic activation ordering is gone: g_idx is now ignored, and the Marlin, GPTQ, CPU and RDNA3 kernels behind it were deleted. The scale-out endpoints /render, /derender and /inference/v1/generate no longer register on a plain vllm serve without --enable-scale-out, and the VLLM_ENABLE_SCALE_OUT_ENDPOINTS variable that used to turn them on was removed. Four items deprecated for 0.29 are now deleted outright, including the VLLM_PREFIX_CACHE_RETENTION_INTERVAL and VLLM_MM_HASHER_ALGORITHM environment variables and the ROCm CUDA_VISIBLE_DEVICES fallback.1

Fast Start adds a persistent per-GPU weight-cache daemon that holds post-quantized, TP-sharded weights in GPU memory, so a restarting engine maps them over CUDA IPC with --load-format ipc_cache instead of reloading from disk. It now covers FP4 checkpoints and multi-node tensor parallelism.

Freezing the garbage collector during CUDA-graph capture cuts capture from 12s to 2s and engine init from 28.9s to 8.2s on an H200, per the release notes. Both figures are vLLM's own, measured on their hardware, not ours.

Also new: Gumbel-max watermarked generation with a keyed PRF and per-request opt-out, and HiSparse, a host-resident KV tier that spills sparse-MLA decode pages to pinned host memory under GPU pressure.

Shipped

02
Use it

Cline CLI 3.0.63 closes a Windows binary-hijack path and stops subagents re-asking for approval

Three fixes in this build are worth the upgrade on their own.4 On Windows, a program planted in your workspace could run in place of the real one, because Windows resolves a bare program name by searching the working directory before PATH. Configured subagents no longer ask you to approve their own tool calls after you have already approved the delegation — with concurrent siblings that was also unsafe, since several children could act on one approval. And compaction now fires on the provider's reported token usage rather than a character estimate, which matters for dense content like disassembly or minified sources.

MATTERS TO · Anyone running the Cline CLI on Windows, and anyone who has delegated work to configured subagents.
nofeed.dev/issues/2026-09-22/cline-cli-3-0-63/
Wait

Grok 4.7 is rolling out in GitHub Copilot, billed at provider list pricing

Available in the model picker across VS Code, Visual Studio, Copilot CLI, the cloud agent, JetBrains, Xcode and Eclipse, for Pro, Pro+, Max, Business and Enterprise.3 It is billed at provider list pricing under usage-based billing, and GitHub says the rollout is gradual, so absence from your picker is expected rather than a fault. We have not evaluated it, and Cursor logged two separate Grok degradations inside the same window.610

MATTERS TO · Copilot Business and Enterprise admins, whose default-enablement policy turns new models on unless they opted out.
nofeed.dev/issues/2026-09-22/copilot-grok-4-7/
The two Cursor incidents, and what they do not prove

Cursor's status page records 0.6 hours of degraded performance on Grok models opening at 01:07 UTC, and 0.4 hours on Grok 4.6 the previous morning. Both are rated minor, and both affected failed or retried requests in Automations, Cloud Agents, the CLI and the IDE. Other models were unaffected in each case.

Those were Cursor's own routing, and no vendor has connected them to Copilot's 4.7 rollout — the two products buy from xAI separately. A new model arriving on a provider path that degraded twice in a day can be worth a week of someone else's testing, which is the whole of our reasoning here.

Promised, not shipped
Nothing was announced-without-shipping in this window that clears the bar. Grok 4.7 is available now but rolling out gradually, so it is printed above as shipped with a Wait.

The conversation

01
The claim — including ours

Rate limits on the paid coding plans are being consumed several times faster than they were two months ago.

From the floor
  • @SimonHoibergreader-posted, unverified

    Reports Sol limits exhausting 4.8-5.9x faster than two months ago, while his own consumption ran about 18% slower. 1,635 likes and 297 replies.

  • @btsouthreader-posted, unverified

    Reports 97% of a weekly Codex limit consumed in under 24 hours after reset, on the $200 tier.

  • @LotusDecoderreader-posted, unverified, disputes the above

    Ran an agent for an hour on Sol and reports the quota bar did not move.

Our take

No vendor has published a change to these allowances, and none of the three accounts shows a method. Self-reported quota bars are not measurement: they mix model routing, cache hit rates and prompt size, and a single figure hides all three. If an allowance genuinely moved, a vendor pricing or limits page will say so, and that is what we will report.

From the ai-dev-x keyword digest, which watches all of X, and the ai-dev-x-accounts digest across 102 accounts. Both were collected at 2026-09-21 05:30 UTC and cover 20-21 September, so they sit roughly 24 hours outside today's window and ran as background only: today's X collection did not land. The Reddit digest folder returned no posts for the last 24 hours, so the Reddit layer did not run either. Hacker News was swept but produced nothing above the noise floor that carried a primary source.

In production

01
1.6 hours

Anthropic logged elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1 and Claude Opus 5, opening at 00:57 UTC and rated major impact. Resolved.2Source · status.anthropic.com, read 2026-09-22

Skip this

06

Everything we saw

115
115 candidates scanned · 3 used in this issue — the rest, with the reason each one was left out
The receipt. Ranking is only trustworthy if the discarded pile is visible, so here it is: everything the collectors surfaced in the window, with its signal and what we did with it.
ItemSourceSignalCall
vLLM v0.30.0GitHub Releases762 commits, 8 breaking itemsLed the issue
Cline CLI v3.0.63 and SDK v0.0.84GitHub ReleasesWindows PATH hijack, subagent approvalsPrinted
Grok 4.7 in GitHub CopilotGitHub ChangelogGradual rollout, list pricingPrinted as Wait
Anthropic: elevated errors, multiple modelsstatus.anthropic.com1.6h, major impactPrinted as the production figure
Cursor: two Grok degradationsstatus.cursor.com0.6h and 0.4h, minorPrinted alongside Grok 4.7
openai-python v3.17.0GitHub ReleasesExternal storage config, safety-case retrievalGenerated SDK surface; watching for the API docs behind it
OpenHands v1.21.0GitHub ReleasesDocker execution workspaces, stale-history fixOne feature, eleven fixes; nothing that changes a decision this week
Vercel: billable duration and CPU minutes on deploymentsVercel ChangelogBilling visibilityUseful, but not an agent-tooling decision
opencode v1.18.32GitHub ReleasesBedrock image hoisting, Together AI usage reportingTwo bugfixes
langgraph 1.2.12 and sdk 0.4.5GitHub Releasesresponse_schema on interrupt(), dependency bumpsMostly dependencies
langchain provider bumps: fireworks 1.6.2, deepseek 1.1.1, openrouter 0.2.9GitHub ReleasesPatch releasesNo decision changes
llama_index v0.14.25GitHub ReleasesPatch releaseNo decision changes
alibaba/open-code-review v1.12.8GitHub Releases+14,499 stars in the windowStar velocity is not a release; patch version, and we printed v1.12.5 as skipped on 18 September
Harness-Zero: Harness Distillation via Agent-as-HarnessarXivAgent harness distillationRead for the argument; no implementation to evaluate
pydantic-ai v2.47.0GitHub ReleasesTwo compatibility notesCut for length; raises on non-str UserPromptPart.content
EOF

End of feed. That is everything from the window worth your time.
Explore more news, analysis and practical guides on NO FEED.

Still developingCompaction is still where the harness fixes cluster. We printed Cline 4.1.19 switching from guesswork to the provider's token accounting on 18 September; today the same change reaches the CLI, alongside a fix for compaction silently degrading to truncation mid-session on OAuth providers.4

The useful part, in your inbox.

One complete edition every weekday, with practical takeaways.