{"version":"2.1.229","anchor":"tool-inputs-are-filtered-before-being-recorded","canonical_anchor":"tool-inputs-are-filtered-before-being-recorded","heading":"Tool inputs are filtered before being recorded","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/tool-inputs-are-filtered-before-being-recorded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Tool inputs are filtered before being recorded\n\nOnly a few named fields of tool input get recorded in history now, and NUL-containing strings are dropped.\n\n**What**\n\nHistory summaries and edited-file tracking no longer read raw tool input. A new helper picks out only `file_path`, `path`, `pattern`, `glob`, `command`, `query` and `content`, and drops any string containing a NUL byte.\n\n**Evidence**\n\n`return typeof e === \"string\" && !e.includes(\"\\x00\");`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}