{"version":"2.1.287","anchor":"runner-clears-an-env-var-in-child-spawns-tools-machine-acce","canonical_anchor":"runner-clears-an-env-var-in-child-spawns-tools-machine-acce","heading":"Sessions clear one more environment variable for programs they start","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/runner-clears-an-env-var-in-child-spawns-tools-machine-acce","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Sessions clear one more environment variable for programs they start\n\nClaude Code now clears one more environment variable for the programs a session starts, and session state tracks a tools machine\n\n**Unclear.** It is not clear which environment variable is cleared or what the tools machine is used for.\n\n**What**\n\nWhen a Claude Code session starts another program, it controls some of that program's environment variables. Environment variables are named settings passed to a program when it starts. One more of them is now cleared before the program starts.\n\nThe session also now keeps track of a tools machine.\n\n**Why**\n\nThis may be part of work on running tools on a separate, remote machine. Nothing here changes what you see.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}