{"version":"2.1.242","anchor":"workflow-tasks-can-relay-the-triggering-request-in-a-labelle","canonical_anchor":"workflow-tasks-can-relay-the-triggering-request-in-a-labelle","heading":"Workflow tasks can relay the triggering request in a labelled frame","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/workflow-tasks-can-relay-the-triggering-request-in-a-labelle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Workflow tasks can relay the triggering request in a labelled frame\n\nWorkflow runs now label whether a person or a schedule triggered them, and quote the request.\n\n**What**\n\nA workflow run now classifies what set it off. A scheduled or external trigger gets an \"automated trigger\" banner telling the model it cannot claim user approval, while a run a person decided relays that person's request verbatim and indented, with optional preceding assistant context, and control characters and backticks stripped.\n\n**Details**\n\n- `CLAUDE_CODE_WORKFLOW_PROMPT_PROVENANCE` forces the behaviour; otherwise it depends on the `tengu_bubbly_harbor` check, which is treated as off if the check fails.\n\n**Evidence**\n\n`[Workflow harness \\u2014 automated trigger]`\n\n- Area: Workflows\n- Names: `CLAUDE_CODE_WORKFLOW_PROMPT_PROVENANCE`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}