{"version":"2.1.312","anchor":"new-telemetryanalytics-names-auto-mode-server-checks-mcp","canonical_anchor":"new-telemetryanalytics-names-auto-mode-server-checks-mcp","heading":"New internal labels for auto mode server checks, MCP approvals and plugin hooks","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/new-telemetryanalytics-names-auto-mode-server-checks-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### New internal labels for auto mode server checks, MCP approvals and plugin hooks\n\nClaude Code now carries new internal labels for server checks in auto mode, an MCP approval ticket, and per-plugin hook counts in usage data\n\n**What**\n\nSeveral new names appear in Claude Code's internal lists:\n\n- `auto_mode_floor_server_check` and `auto_mode_no_server_check`, two labels relating to auto mode (where Claude Code decides on its own whether to allow an action)\n\n- `mcp_approval_ticket`, a label relating to MCP (the system that connects Claude Code to outside tools)\n\n- `pluginHookCountsByHash`, a new field allowed in usage data, relating to how many hooks each plugin has\n\n**Why**\n\nThese point to auto mode checking with a server in some cases and to an approval-ticket step for MCP tools. Nothing here says how either behaves yet.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}