{"version":"2.1.248","anchor":"four-tools-now-declare-that-they-run-code","canonical_anchor":"four-tools-now-declare-that-they-run-code","heading":"Four tools now declare that they run code","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/four-tools-now-declare-that-they-run-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Four tools now declare that they run code\n\nFour tools now declare that they can run code, which permission logic reads.\n\n**What**\n\nThe session-requeue and local-runner-spawn admin tools, along with the PowerShell tool and cron job creation, now carry a flag marking them as capable of executing code. This is a declaration read by permission and classification logic, not a change to what the tools do.\n\n**Details**\n\n- The two runner tools already required classifier review in auto mode and prompted otherwise.\n\n**Evidence**\n\n`enablesCodeExecution`, `start a local self-hosted runner process for try-it-out`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}