{"version":"2.1.286","anchor":"system-prompt-boundary-telemetry-can-be-skipped","canonical_anchor":"system-prompt-boundary-telemetry-can-be-skipped","heading":"Some system prompt usage reports can now be switched off by the caller","tier":"internal","area":"System Prompt","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/system-prompt-boundary-telemetry-can-be-skipped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Some system prompt usage reports can now be switched off by the caller\n\nThree usage reports sent while splitting the system prompt now fire only when the calling code does not ask to skip them\n\n**Unclear.** It is not clear which parts of Claude Code ask to skip these reports.\n\n**What**\n\nThe system prompt is the set of instructions Claude Code gives the model before your messages. When Claude Code splits it into parts, it sends usage reports: whether it found the marker between parts, whether that marker was missing, and whether it used tool-based caching. These reports used to always be sent. Code that splits the prompt can now ask for them to be skipped.\n\n**Why**\n\nThis cuts repeated reports from code other than the main session that also splits the system prompt.\n\n- Area: System Prompt\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}