{"version":"2.1.315","anchor":"env-var-expansion-skips-strings-with-no","canonical_anchor":"env-var-expansion-skips-strings-with-no","heading":"Text with no ${ is no longer run through environment variable expansion","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/env-var-expansion-skips-strings-with-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Text with no ${ is no longer run through environment variable expansion\n\nClaude Code now leaves text containing no ${ untouched instead of fully parsing it for environment variable references\n\n**Unclear.** It is not clear whether the full parsing step ever changed text that has no ${ in it, which this shortcut would now skip.\n\n**What**\n\nClaude Code can fill in environment variables written as `${NAME}` inside text. An environment variable is a named value set in your shell or system. When a piece of text contains no `${` at all, Claude Code now returns it exactly as it was, straight away. Before, every piece of text went through the full parsing step, even when there was nothing in it to replace.\n\n**Why**\n\nThis is mainly a speed improvement. Text with `${NAME}` references in it is handled as before.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}