{"version":"2.1.323","anchor":"editor-spawns-get-a-sanitized-env","canonical_anchor":"editor-spawns-get-a-sanitized-env","heading":"Your external editor now gets environment variables chosen by Claude Code","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/editor-spawns-get-a-sanitized-env","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Your external editor now gets environment variables chosen by Claude Code\n\nWhen Claude Code opens your external editor, it now passes a set of environment variables it builds instead of passing its own unchanged\n\n**Unclear.** It is not clear which environment variables are removed or added for the editor.\n\n**What**\n\nWhen Claude Code opens an external editor, such as the program named in `$EDITOR`, it now passes the editor a set of environment variables that it builds itself. Environment variables are named settings a program reads when it starts. Before, the editor got the same variables Claude Code was running with.\n\n**Why**\n\nIf your editor depends on a particular environment variable, it may now see a different value or none at all.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}