What probably matters to youSection of the release
Unclear Whether this is already exposed as a usable tool, or is unreleased backing code, is not stated.
What
New 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.
Why
If 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.
process.envAgent SDK reference - TypeScriptmodified, high confidence| `env` | `Record<string, string \| undefined>` | `process.env` | Environment variables. When set, this replaces the subprocess environment instead of merging with `process.env`, so pass `{ ...process.env, YOUR_VAR: 'value' }` to keep inhe…see the edit
Since it was published
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up process.env, on Modifying system prompts.Pass settings keys through the [`settings`](/docs/en/agent-sdk/typescript#options) option in TypeScript or [`settings`](/docs/en/agent-sdk/python#claudeagentoptions) in Python, and environment variables through the `env` option. In TypeScr…agent-sdk/modifying-system-promptssee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether this is already exposed as a usable tool, or is unreleased backing code, is not stated.
Anthropic's documentation agreesprocess.env on Agent SDK reference - TypeScript
