{"version":"2.1.271","anchor":"sdk-control-responses-can-now-redact-persisted-lane-data-mc","canonical_anchor":"sdk-control-responses-can-now-redact-persisted-lane-data-mc","heading":"Control-plane responses can now be redacted for hosted\/background sessions","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/sdk-control-responses-can-now-redact-persisted-lane-data-mc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Control-plane responses can now be redacted for hosted\/background sessions\n\nSDK control responses like get_context_usage and get_usage now strip sensitive detail for hosted\/background sessions\n\n**Unclear.** The finding does not say which sessions or lanes trigger redactsPersistedLane, or why.\n\n**What**\n\n- New helper functions check whether a session `redactsPersistedLane()` (true for hosted\/background sessions where the transport persists) and, when true, strip sensitive detail from SDK control responses.\n\n- `get_context_usage` responses omit `memoryFiles`, and `get_usage` responses exclude usage `behaviors` data when the session's lane is redacted.\n\n- MCP server config secrets are also stripped from responses in this case.\n\n**Why**\n\nThis prevents potentially sensitive details, such as memory file contents, MCP config secrets, or usage behavior data, from being returned over the SDK control channel for hosted or background sessions where that data shouldn't be exposed.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}