{"version":"2.1.227","anchor":"settings-environment-state-moved-onto-one-object","canonical_anchor":"settings-environment-state-moved-onto-one-object","heading":"Settings environment state moved onto one object","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/settings-environment-state-moved-onto-one-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Settings environment state moved onto one object\n\nSettings-driven environment variables and plugin paths are now handled by one resettable object.\n\n**What**\n\nApplying environment variables from settings layers, the rules that let managed telemetry settings win, the snapshot of the environment taken before settings load, and the set of keys passed to spawned hosts are now fields on a single object, so resetting them is one call. Plugin cache and marketplace paths can now be turned into storage keys, and plugin MCP server files read through the backend.\n\n**Evidence**\n\n`so lower-trust scopes cannot redirect `\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}