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.273 ·

Tool-execution hook context object substantially reworked

The context object passed to tool-execution hooks was substantially reworked with many new fields

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaHookswhat it touches
KindInternal Changesin v2.1.273,
Under the hood

The context object passed to tool-execution hooks was substantially reworked with many new fields

What

The context object handed to tool-execution hooks (code that runs around a tool call) was rebuilt. It no longer includes credentials, isNonInteractiveSession, persistedToolResultFiles, artifactRead, or signal. In their place it now carries a much larger set of fields, including agentId, agentWorktree, taskRegistry, readFileState, getFileHistoryState, applyFileHistoryOp, sessionEnvVars, markPrResolvedThisSession, userTypedShellDispatch, emitToolProgress, shellPermission (bundled with abortController and toolUseId), mainLoopModel, effort, effortLayerOverride, unlayeredPermissions, abortController, remoteCall, and innerCall.

Why

This substantially expands what internal hooks and tool-execution code can see and do around a tool call, covering things like agent identity, file-history tracking, and per-call permissions and effort settings, rather than the narrower context passed before.

See this entry in the whole of v2.1.273 →

Feedback