{"version":"2.1.299","anchor":"tool-use-summaries-trimmed-session-metadata-keptby-field","canonical_anchor":"tool-use-summaries-trimmed-session-metadata-keptby-field","heading":"Tool-use summaries are cleaned before use, and sessions record who kept them","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/tool-use-summaries-trimmed-session-metadata-keptby-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Tool-use summaries are cleaned before use, and sessions record who kept them\n\nTool-use summary text is now cleaned up before Claude Code checks whether it is empty, and session records note which process kept a session\n\n**What**\n\nWhen Claude uses a tool (an action such as reading a file or running a command), Claude Code can show a short summary of it. That summary text is now cleaned up before Claude Code checks whether it is empty. Claude Code's internal list of sessions (a session is one conversation with Claude) also gains a field recording which process kept a session, by its process ID and start time.\n\n**Why**\n\nThese are small internal adjustments. In practice, a summary containing nothing meaningful should now be treated as empty.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}