Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.274 ·

Tool list access consolidated into a shared toolCatalog

Session and permission setup now pass tool-list access (getAllBaseTools, getTools, assembleToolPool) through a shared toolCatalog object instead of calling separate global functions.

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal0worth watching, 1 to 5
AreaPermissionswhat it touches
KindInternal Changesin v2.1.274,
Group of 2 Under the hood

Session and permission setup now pass tool-list access (getAllBaseTools, getTools, assembleToolPool) through a shared toolCatalog object instead of calling separate global functions.

What

  • The code that builds the tool permission context (which tools are allowed/disallowed, including --tools narrowing) now receives getAllBaseTools as an explicit parameter instead of calling a fixed global function directly.
  • Session and agent setup (main loop, subagents, resumed sessions) now threads a shared toolCatalog object ({ getAllBaseTools, getTools, assembleToolPool }) through options, alongside the existing tools field, replacing scattered direct calls.

Why This is an internal cleanup that makes tool-list access consistent and explicit across the codebase, reducing the chance of different code paths using mismatched or stale tool lists.

See this entry in the whole of v2.1.274 →

Feedback