Claude Code 2.1.302: the three default changes to check before you upgrade

Claude Code v2.1.302 was tagged on 16 October 2026, and most of its entry list is ordinary fixes. Nine entries carry the changelog's "Changed" marker, and three of those change defaults that decide how a session runs: for non-interactive sessions on third-party providers, for fork subagents, and for where the desktop app and VS Code run subagents. If you script Claude Code or run it in an editor, those three are the ones to read before you upgrade, because nothing about them requires you to opt in.

#Which defaults changed?

The changelog's wording is specific about where each change applies, and the surface matters more than the version number here. Nine entries in this release carry the project's own marker for behaviour that was already working one way: seven begin with the word "Changed", and two more sit under a [Claude Tag] prefix. Three of those nine change how a session itself runs, and they are the ones below.

Default	Before	In v2.1.302	How to override
Permission mode in claude -p and the Agent SDK, on third-party providers, with telemetry off or on a fresh install	Not default mode	Starts in default mode	Pass --permission-mode auto, which the entry says keeps auto
Fork subagents (subagent_type: "fork") in claude -p, the Agent SDK, the desktop app and VS Code	Off in those four; already on in the terminal	On by default	CLAUDE_CODE_FORK_SUBAGENT=0
Where the desktop app and VS Code run the main conversation's subagents	Claude chose	Always in the background, as the terminal does	Not named in the entry

The permission-mode change is the one to check first if you run Claude Code unattended. The changelog states it as: "Changed claude -p and Agent SDK sessions with no permission mode to start in default mode on third-party providers, with telemetry off or on a fresh install; --permission-mode auto keeps auto." Read the conditions closely. It is scoped to third-party providers and to sessions that named no mode at all, so a script that already passes --permission-mode is untouched. A script that did not, and relied on whatever it got, is the case this changes.

The fork-subagent entry is a consistency change rather than a new capability: fork subagents were already on in the terminal, and 2.1.302 brings the other four surfaces into line. The entry also records two boundaries worth keeping: CLAUDE_CODE_FORK_SUBAGENT=0 turns them off, and claude mcp serve never offers them at all.

The third entry has a second half that pulls the opposite way, and quoting it in full is the only honest way to report it: the desktop app and VS Code now always run the main conversation's subagents in the background, "rather than let Claude choose", while "a subagent's own Agent calls in claude -p, the Agent SDK, the desktop app and VS Code now run in the foreground by default". So the nesting level decides the direction, and a reader who takes away only "subagents moved to the background" has half of it.

#What else is in the release?

Four more entries stood out to us for anyone running agents in anger, three fixes and one further change:

• A memory limit on image reads. The changelog records a fix for "the Read tool loading an image file of any size, or a pipe or device named like an image, entirely into memory", and says image sources over 128 MB are now refused. The named device case is the interesting half: a path that looks like an image but is a pipe was previously read as one.
• An MCP protocol mismatch. MCP servers could show no tools, or fail every tool call, when the server negotiates protocol version 2026-07-28 but omits resultType, ttlMs or cacheScope. If a server of yours went quiet recently and you have been looking at your own configuration, look at this entry instead.
• A scheduled run that could repeat its work. Under cloud sessions, the changelog records a fix for "a scheduled routine run that failed partway being run again from the start an hour or more later, which could repeat work such as posting the same report twice". Anyone running a routine that writes somewhere other people can see has a reason to know this happened.
• A cap on concurrent hooks. This one is a change rather than a fix: "Changed prompt and agent hooks so that at most 12 of one event run at a time; the rest wait their turn". It needs no opt-in, so if you fan out more than a dozen hooks on a single event, the extras now queue instead of all running at once.

Two smaller additions are worth a line. CLAUDE_CODE_AUTO_MODE_MODEL now chooses the model the client-side auto mode classifier uses, and the changelog is explicit that it "does not change the model for server-side auto mode", so it is not a single switch for both. And /config gains an Idle compaction row for turning idle compaction off or back on, with the post-compaction notices now saying how to turn it off.

#Is Claude Design closing?

One entry in this release is an announcement rather than a change to Claude Code, and it is the only place we found it. The changelog says v2.1.302 "Added a notice to /design-sync and /design-login that standalone Claude Design (claude.ai/design) closes by December 14, 2026".

We are reporting that as what it is: Anthropic's own repository recording that Claude Code now shows that notice in two commands. We looked for a separate announcement or help-centre page carrying the same date and did not find one on the pages we checked, so if you depend on claude.ai/design, treat the in-product notice as the thing to go and read rather than taking a date from us. The changelog entry is a primary source for the notice existing; it is not a substitute for Anthropic's own page about the product, which may say more about what "standalone" excludes.

#How fast is Claude Code shipping now?

Fast enough that the version you are on is probably not the newest one. The tag list puts v2.1.302 on 16 October 2026, v2.1.301 on 15 October, and v2.1.300 and v2.1.299 both on 14 October. That is four releases in three days, and it is the reason a changelog entry is a better thing to search than a release name: the behaviour you are chasing probably changed in a point release nobody wrote a post about.

It also means the practical upgrade advice is unchanged from any other week. Check claude --version against the tag list, read the entries between the two, and pay attention to the ones beginning "Changed", because those are the only kind that alter something you already had working.

#Where to go next

If the subagent changes above are new territory, our guide to Claude Code subagents covers what they are and when to reach for one. For the extension point that runs inside the agent with your permissions, Claude Code mods is the one to read, and the Claude Code hub carries the platform facts we keep verified.

#What we could not confirm

The changelog file itself carries no dates, so every date in this article comes from the tag and release pages rather than from the entry list. The release page for v2.1.302 records "16 Oct 20:53" with no year and no time zone shown; we read the year from the tag listing, which dates the same tag 16 October 2026.

We have not run the three changed defaults to observe them, so this article reports what the release notes say changed, not a test of each one on each surface. The Claude Design closure date rests on the single changelog entry quoted above and nothing else we could find.