{"version":"2.1.287","anchor":"env-from-unpinneduntrusted-served-folders-is-filtered","canonical_anchor":"env-from-unpinneduntrusted-served-folders-is-filtered","heading":"Environment variables from untrusted served folders are held back","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/env-from-unpinneduntrusted-served-folders-is-filtered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Environment variables from untrusted served folders are held back\n\nClaude Code now withholds environment variables set by a served folder that nobody has trusted\n\n**Unclear.** It is not clear what a served folder is in practice, what triggers this filtering, or whether it is switched on for everyone.\n\n**What**\n\nSettings can set environment variables, which are named values that programs read when they start. Claude Code now filters out such variables when they come from a served folder that nobody has trusted, and it keeps track of whether it held any back.\n\nA starting folder without a trust marking is also now treated as private by default.\n\n**Why**\n\nThis appears to tighten what outside or shared settings can change in your environment without your trust.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5"}