{"version":"2.1.248","anchor":"cloud-sessions-consider-the-running-process-environment-when","canonical_anchor":"cloud-sessions-consider-the-running-process-environment-when","heading":"Cloud sessions consider the running process environment when offering hooks","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cloud-sessions-consider-the-running-process-environment-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cloud sessions consider the running process environment when offering hooks\n\nCloud sessions include the running process environment when deciding which hooks this machine offers.\n\n**What**\n\nWhen a cloud session works out which hooks this machine offers, it now also takes the current process environment into account when building the shell prefix's own environment, alongside the environment attached to the session and the one captured before settings loaded. Only applies when hook consent is set to cloud; the user-facing explanations are unchanged.\n\n**Evidence**\n\n`All hooks were switched off in your settings during this cloud session; for it, this machine keeps offering the hooks it had when you launched (listed here) until you restart claude --cloud.`\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}