{"version":"2.1.323","anchor":"ripgrep-child-processes-now-get-a-sanitized-env","canonical_anchor":"ripgrep-child-processes-now-get-a-sanitized-env","heading":"File searches now run ripgrep with a cleaned-up set of environment variables","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/ripgrep-child-processes-now-get-a-sanitized-env","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### File searches now run ripgrep with a cleaned-up set of environment variables\n\nClaude Code now starts ripgrep with a filtered set of environment variables instead of passing on all of its own\n\n**Unclear.** It is not stated which environment variables are kept or removed, so settings passed to ripgrep through the environment may no longer reach it.\n\n**What**\n\nripgrep is the program Claude Code uses to search files. Environment variables are named settings that a program passes to the programs it starts. Every time Claude Code starts ripgrep, it now passes a filtered set of them instead of all of its own. This covers searches, file counts and the check that ripgrep works. That check also no longer adds Claude Code's full set of variables on top.\n\nOther changes:\n\n- File counting stops early for a path when that path, or a folder above it, matches a certain check.\n\n- ripgrep output that arrives after a search was cancelled is now ignored.\n\n**Why**\n\nThis looks like protection against environment variables changing how ripgrep behaves when Claude Code runs it.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}