{"version":"2.1.275","anchor":"internal-tool-use-tracking-state-reworked","canonical_anchor":"internal-tool-use-tracking-state-reworked","heading":"Internal tool-use tracking state reworked","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/internal-tool-use-tracking-state-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Internal tool-use tracking state reworked\n\nInternal per-session tool-tracking state replaced caching fields with tool-lifecycle and nested-agent bookkeeping\n\n**Unclear.** The finding doesn't state what user-facing behavior, if any, this internal rework affects.\n\n**What**\n\nA piece of internal per-session state that used to cache `markdownTokens`, `highlightedCode`, and `structuredDiff` data has been reworked. It now instead tracks `retracted`, `inProgressToolUses`, `evictedToolUses`, and `nestedUuidAliases`.\n\n**Why**\n\nThis appears to shift the bookkeeping from rendering-related caches toward tracking the lifecycle of tool calls (in progress, evicted) and aliasing identifiers for nested agents, though the visible effect of this internal change isn't specified.\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}