{"version":"2.1.271","anchor":"plugin-sandbox-now-conditionally-installs-timerconsole-glob","canonical_anchor":"plugin-sandbox-now-conditionally-installs-timerconsole-glob","heading":"Plugin sandbox now conditionally installs timer\/console globals","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/plugin-sandbox-now-conditionally-installs-timerconsole-glob","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Plugin sandbox now conditionally installs timer\/console globals\n\nPlugin sandbox now installs timer and console globals only when asked\n\n**What**\n\nThe setup function for a plugin's sandboxed JavaScript environment (a restricted execution context plugins run in) now takes its options as a destructured object with a new `isInstallingGlobals` flag. Installing `setTimeout`, `setInterval`, `clearTimeout`, `clearInterval`, and `console` into that sandboxed environment now only happens when this flag is set, instead of always happening.\n\n**Why**\n\nThis gives Claude Code finer control over what a plugin sandbox is given access to, letting some sandboxes skip these globals entirely rather than always installing them.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}