Under the hood
Tool execution context gains new internal capabilities for file history, read deduplication, and isolation
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, andapplyFileHistoryOp, for tracking and modifying file historydynamicSkillDirTriggersandnestedMemoryAttachmentTriggers, related to skills and memory attachmentdedupUnchangedReads,setArtifactReadVersion, andgetArtifactReadObservation, related to deduplicating unchanged file readsturnMcpClientsandisolationLatch
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).
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What most of these new fields (agentWorktree, isolationLatch, turnMcpClients, etc.) actually enable for tools is not shown by the evidence.