{"version":"2.1.267","anchor":"new-processenv-readwrite-primitive-for-tools","canonical_anchor":"new-processenv-readwrite-primitive-for-tools","heading":"New process.env read\/write primitive for tools","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-processenv-readwrite-primitive-for-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New process.env read\/write primitive for tools\n\nNew internal helpers let Claude read and set process environment variables\n\n**Unclear.** Whether this is already exposed as a usable tool, or is unreleased backing code, is not stated.\n\n**What**\n\nNew internal functions read a `process.env` variable by name, validate a name\/value pair before writing (rejecting names containing `=` or NUL bytes, and rejecting non-string values), and set or delete a `process.env` entry (deleting it when the value given is undefined). This looks like the backing implementation for a capability that lets Claude get or set environment variables for the current process.\n\n**Why**\n\nIf exposed as a tool, this would let Claude inspect or change environment variables directly rather than only through shell commands, with basic validation to reject malformed names or values.\n\n- Area: SDK\n- Names: `process.env`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 5\/5"}