Fork subagents are on by default, open weights split in two, and Claude Design gets an end date

A quiet window, and I’d rather say so than pad it. Nothing on the Disruption Watch moved up a rung. The two things worth your time are a default change in Claude Code that affects every scripted run, and a split in what “open weights” means for client work.

The top 3

1. Claude Code 2.1.302 turned fork subagents on for scripted use

Fork subagents are now on by default in claude -p, the Agent SDK, the desktop app and VS Code. CLAUDE_CODE_FORK_SUBAGENT=0 switches them off. The desktop app and VS Code now run the main conversation’s subagents in the background, and at most 12 prompt or agent hooks for one event run at once; the rest queue. The release also adds CLAUDE_CODE_AUTO_MODE_MODEL to pick the model for the client-side auto-mode classifier.

Why it matters: any unattended job (scheduled routines, CI scripts, anything on the SDK) may now spawn forks that inherit context. That changes both cost and what your agent.spawn hooks see, without you touching a line. Re-run one scheduled job and compare tokens before and after the upgrade.

Source: Claude Code CHANGELOG, 2.1.302

2. Open weights got cheap in two different ways

Meta published Muse Spark Open weights on 15 October: 816B parameters, 42B active, 1M context, under a custom “Muse Model License” with limited commercial terms. One outlet reports a $20M revenue threshold; I couldn’t confirm the terms, and the benchmarks are Meta’s own. Separately, DeepSeek released V4.1 Flash under MIT in September, then began routing V4-Pro requests to Flash at Flash rates, about $0.30 in and $1.20 out per million tokens at peak.

Why it matters: “open” now splits into MIT, which you can build into a client product, and licence-gated, where you need to read the clause before you quote. And a lab retiring its top model into a cheap tier is a pricing move, not only a release. The client question becomes “why am I paying for the big tier?”

Sources: The New Stack, Trending Topics on the licence, The Next Web, TechNode

3. Standalone Claude Design closes on 14 December 2026

In 2.1.302, /design-sync and /design-login warn that standalone Claude Design shuts on 14 December 2026. The changelog is the only source; I found no Anthropic post, so what happens to existing designs is unknown.

Why it matters: a design-generation product from a frontier lab is being retired or folded in within months of launch. If any work lives there, export it now. More broadly, treat generated-design tools as unstable suppliers, not a stable layer to build a service on.

Source: Claude Code CHANGELOG, 2.1.302

Signal radar

Early signals, before they’re news. Being wrong here is acceptable; being obvious isn’t.

MCP servers on spec 2026-07-28 are failing when they omit three fields

ACT NOW Medium confidence.

2.1.302 fixed handling of servers on that protocol version that omit resultType, ttlMs or cacheScope, which had caused missing tools or failed calls. Spec adopters are shipping partial implementations and clients are tolerating it by patch. If you publish or run an MCP server, set all three explicitly rather than relying on the client’s leniency.

Source: Claude Code CHANGELOG, 2.1.302

Gateways don’t honour MCP tool annotations yet

WATCH Medium confidence, unverified.

A LiteLLM issue (#44093, reported in the agents-radar digest; I didn’t read the issue itself) says MCP tool pins ignore outputSchema and readOnlyHint. If a read-only hint is lost at the proxy, a policy that relies on it silently stops working. This is the second week of “MCP at the gateway” items, and the first correctness bug in that pattern.

Source: agents-radar, AI Infrastructure Digest, 19 October

Research frontier

No paper this window that I could read at source, and I won’t explain a paper from its title. Back next issue.

New capabilities to adopt

Decide on fork subagents for every unattended job

ACT NOW

Run one scheduled job twice, once with CLAUDE_CODE_FORK_SUBAGENT=0, and compare tokens and results. About 15 minutes.

Put the auto-mode classifier on a cheaper model

ACT NOW

CLAUDE_CODE_AUTO_MODE_MODEL sets the model that checks tool calls in client-side auto mode, so permission checks don’t have to use your main model. Try a small model and watch for over-blocking. About 10 minutes.

Classifier telemetry and a hook concurrency cap

WATCH

2.1.301 adds classifier_verdict, permission_mode and classifier_category to tool_decision events, so you can see why something was allowed or denied. Worth wiring only if you already export OpenTelemetry. And since more than 12 prompt or agent hooks on one event now queue, keep model-calling hooks few.

Source: Claude Code CHANGELOG, 2.1.301 and 2.1.302

Disruption watch

No entry moved. The full board, with history, is on the Watch page.

• Ultra-cheap and open-weight models: Repricing the work. Held; Muse Spark Open and DeepSeek V4.1 Flash add evidence.
• Design generation: Accelerating. Held; Claude Design closing is consolidation, not a breakthrough.
• Harness and plugin layer: Hitting the market. Held; more control surface, no new rung.
• MCP and tool protocols: Repricing the work. Held; partial spec implementations being patched around.
• Everything else held, several for lack of new evidence rather than after a fresh check: app generation, autonomous QA and AI-native infrastructure had no dated news this window.

Practice shifts

Treat harness defaults as dependencies, and pin them

ACT NOW

List the environment variables and settings your unattended jobs depend on: CLAUDE_CODE_FORK_SUBAGENT, model aliases that can now fall back silently, the auto-mode model. Pin them explicitly and note the version you tested against. Two defaults changed in one release.

Run the classifier and the router on a cheaper tier than the worker

WATCH

A settable classifier model, cheap open-weight tiers and decision-style endpoints all point the same way: a small model for allow, deny and route, a larger one for the work. Measure agreement on a labelled sample before you trust it.

Check licences the way you check prices

CONTEXT

“Open weights” no longer means “I can ship this to a client”. Put a licence line next to the price line in any model comparison you send.

This week’s experiment

Measure what fork subagents change in your own setup. 45–60 minutes.

Build: in a throwaway repo, scaffold a Claude Code mod with one agent.spawn hook (the built-in plugin-authoring skill does the scaffolding). The hook appends agentId, model and the first 200 characters of the prompt to .claude/spawn-log.jsonl, and rewrites model to the Haiku alias for any workflow agent whose prompt starts with “search” or “triage”. Run the same three-subagent task twice, with and without CLAUDE_CODE_FORK_SUBAGENT=0.

Done when:

1. The log has one row per spawned agent in both runs, and you can say whether the hook fired for forks.
2. At least two agents were rewritten to Haiku.
3. You’ve broken the hook on purpose and noted whether the spawn was refused or went through.
4. Your README has one line with the token difference between the two runs.

---

Sourcing: Anthropic’s newsroom had no developer-facing post in this window. Items marked unverified come from community digests rather than primary sources.