{"version":"2.1.282","anchor":"session-history-transcripts-drop-api-request-lines-when-thir","canonical_anchor":"session-history-transcripts-drop-api-request-lines-when-thir","heading":"Session history sent from your machine now leaves out API request records","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/session-history-transcripts-drop-api-request-lines-when-thir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Session history sent from your machine now leaves out API request records\n\nWhen third-party transcripts are excluded, session history now strips API request lines and replaces unreadable lines with a size-only placeholder\n\n**Unclear.** Which feature collects this session history is not stated.\n\n**What**\n\nClaude Code can send a copy of a session's raw transcript (the saved record of the conversation) as part of session history. When the caller asks to exclude third-party transcripts and the transcript passes the check for third-party markers, it is now filtered line by line before it is sent:\n\n- Lines recording API requests are removed.\n\n- Lines that cannot be read, have no recognisable type, or contain an API request marker are replaced with a placeholder that only gives their size.\n\nTranscripts that contain third-party markers are still withheld entirely, as before. Previously, a transcript that passed the check was sent unchanged, API request lines included.\n\n**Why**\n\nLess raw API request data leaves your machine when session history is collected.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}