{"version":"2.1.208","anchor":"ripgrep-null-byte-protection","canonical_anchor":"ripgrep-null-byte-protection","heading":"Ripgrep null byte protection","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208\/e\/ripgrep-null-byte-protection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208","markdown":"### Ripgrep null byte protection\n\n**What**\n\nRipgrep (used by the Grep tool) now refuses to spawn if any argument, the target path, or the session working directory contains a null byte (`\\0`). Previously, this could produce confusing failures deep in process spawning.\n\n**Details**\n\n- Throws `RipgrepNullByteError` with a specific message identifying which argument contains the null byte\n- Checked in order: session cwd, target path, caller arguments\n- The check happens before spawning, so the error is surfaced at the tool level rather than as a cryptic OS error\n\n**Evidence**\n\nNull byte guard (search for `\"ripgrep spawn blocked: null byte in session cwd\"`)"}