Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.314entry #10

Claude Code v2.1.314 ·

New CLAUDE_CODE_UPFRONT_TOOLS variable picks tools to load at the start

Setting CLAUDE_CODE_UPFRONT_TOOLS to a list of tool names makes those tools load at the start instead of being held back until needed

Use it now Notable No documentation found New Features
JSON All of v2.1.314
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Tool LoadingArea: what it touches
New FeaturesKind: in v2.1.314,
What probably matters to youSection of the release

Unclear How the tool names in CLAUDE_CODE_UPFRONT_TOOLS should be separated is not stated.

What

Claude Code can hold some tools back and only load them when Claude needs them, which is called deferring them. A new environment variable (a setting passed to a program when it starts), CLAUDE_CODE_UPFRONT_TOOLS, takes a list of tool names. Tools on the list are not deferred while the set of tools for the session has not yet been decided.

Some details:

  • MCP tools that come from claude.ai are never affected.
  • The variable is passed on to helper processes Claude Code starts, so it reaches them too.
  • Claude Code never sets it itself. Whatever launches Claude Code has to supply it.
  • The number of names given is recorded in usage data.
Why

Whoever launches Claude Code can now choose which tools are loaded from the start, rather than waiting until Claude asks for them.

Read from
Names in the bundleCLAUDE_CODE_UPFRONT_TOOLS
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtHow the tool names in `CLAUDE_CODE_UPFRONT_TOOLS` should be separated is not stated.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_UPFRONT_TOOLS

See this entry in the whole of v2.1.314 →

Feedback