{"version":"2.1.317","anchor":"daemon-bg-status-drops-fields-tool-meta-adds-memory-and-jit","canonical_anchor":"daemon-bg-status-drops-fields-tool-meta-adds-memory-and-jit","heading":"MCP tool results now carry background-process memory figures","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/daemon-bg-status-drops-fields-tool-meta-adds-memory-and-jit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### MCP tool results now carry background-process memory figures\n\nResults from Claude Code's MCP server tools now include memory figures for its background process, and its status report drops several fields\n\n**Unclear.** It is not clear whether these memory figures are sent every time or only in some modes.\n\n**What**\n\nClaude Code can run as an MCP server, so other programs can use its tools. The results of those tools now carry extra details:\n\n- Memory: `daemon_rss_mib`, `daemon_anon_mib` and `daemon_peak_rss_mib`, which measure how much memory Claude Code's background process uses.\n\n- Tuning: `jit_policy`, `collection_timer_off` and `start_tuning`.\n\nThe count of programs left running now includes sessions being followed.\n\nThe status report for that background process no longer includes the supervisor version or uptime, `controlSock`, `serviceInstalled` or `configuredWorkers`.\n\n**Why**\n\nMemory figures for the background process now come with tool results, while some fields that status checks may have relied on are gone.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}