{"version":"2.1.280","anchor":"new-telemetry-event-plugin-function-hooks-pane-ask","canonical_anchor":"new-telemetry-event-plugin-function-hooks-pane-ask","heading":"New telemetry event: plugin_function_hooks_pane_ask","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-telemetry-event-plugin-function-hooks-pane-ask","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New telemetry event: plugin_function_hooks_pane_ask\n\nNew telemetry events added for plugin hooks pane, MCP resource reads, and artifact live edits; one old event removed\n\n**What**\n\nSeveral telemetry event\/gate identifiers changed:\n\n- `plugin_function_hooks_pane_ask` is a new event fired when a plugin function-hooks pane's 'asked' persistence state changes, either recorded successfully or failed with reason `not_persisted`.\n\n- `mcp_read_resource` is a new identifier added alongside existing MCP-related entries like `mcp_reconnect` and `mcp_oauth_revoke`.\n\n- `artifact_live_edit_reissue` is a new event added alongside existing artifact events `artifact_live_push` and `artifact_live_subscribe`.\n\n- `repl_clear_view` was removed from the telemetry allowlist, and a related `replCount` field was dropped from a usage-aggregation object.\n\n**Why**\n\nThese changes track new behaviors (plugin hook panes, MCP resource reads, artifact live-edit reissues) while retiring telemetry for a REPL clear-view action that's no longer tracked.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}