{"version":"2.1.251","anchor":"workflow-scripts-must-be-paths-the-tool-already-surfaced","canonical_anchor":"workflow-scripts-must-be-paths-the-tool-already-surfaced","heading":"Workflow scripts must be paths the tool already surfaced","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/workflow-scripts-must-be-paths-the-tool-already-surfaced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Workflow scripts must be paths the tool already surfaced\n\nWorkflow scripts only run from paths you can already read, and refusals say why.\n\n**What**\n\nA workflow script path is now refused unless it is a path the tool itself returned or a file you can already read, meaning one under the working directory or an added directory. The refusal states the rule explicitly instead of the path being used silently.\n\n**Details**\n\n- Applies unconditionally, with no flag to relax it.\n\n**Evidence**\n\n`scriptPath must be a script path this tool returned, or a file you can already read`\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}