{"version":"2.1.269","anchor":"plugin-desktop-surface-tracking-and-per-module-hashing-added","canonical_anchor":"plugin-desktop-surface-tracking-and-per-module-hashing-added","heading":"Plugin desktop-surface tracking and per-module hashing added","tier":"internal","area":"Plugin UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/plugin-desktop-surface-tracking-and-per-module-hashing-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin desktop-surface tracking and per-module hashing added\n\nClaude Code now tracks which UI surfaces a plugin's components render into and can hash a plugin's linked files\n\n**Unclear.** What user-facing feature uses this surface-tracking and hashing is not specified.\n\n**What**\n\nNew internal infrastructure tracks which UI 'surfaces' (such as the desktop app) a plugin's rendered components are attached to, keyed by a client identifier. A related addition computes a content hash covering a plugin's linked files, modules, and runtime limits.\n\n**Why**\n\nThis groundwork lets Claude Code know where a plugin's UI is currently showing and detect when a plugin's linked content has changed, though the finding doesn't specify what feature will consume this tracking yet.\n\n- Area: Plugin UI\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}