Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.265entry #319

Claude Code v2.1.265 ·

Tool execution context exposes new capabilities: file history, dedup, isolation latch

Tool execution context gains new internal capabilities for file history, read deduplication, and isolation

Under the hood Internal Changes
JSON All of v2.1.265
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Tooling ArchitectureArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release

Unclear What most of these new fields (agentWorktree, isolationLatch, turnMcpClients, etc.) actually enable for tools is not shown by the evidence.

What

The internal context object passed to tool calls (the data each tool gets access to when it runs) gained a batch of new capabilities, including:

  • agentWorktree, readFileState, getFileHistoryState, and applyFileHistoryOp, for tracking and modifying file history
  • dynamicSkillDirTriggers and nestedMemoryAttachmentTriggers, related to skills and memory attachment
  • dedupUnchangedReads, setArtifactReadVersion, and getArtifactReadObservation, related to deduplicating unchanged file reads
  • turnMcpClients and isolationLatch
Why

This is internal plumbing that expands what tools can access during execution. The evidence doesn't describe a user-visible behavior change beyond what's already documented for dedupUnchangedReads (which lets an individual read opt out of the existing suppression of re-reads of unchanged files).

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 doubtWhat most of these new fields (agentWorktree, isolationLatch, turnMcpClients, etc.) actually enable for tools is not shown by the evidence.

See this entry in the whole of v2.1.265 →

Feedback