{"version":"2.1.300","anchor":"workflow-launch-records-carry-a-hidden-script-digest","canonical_anchor":"workflow-launch-records-carry-a-hidden-script-digest","heading":"Workflow launch records can now carry a fingerprint of a hidden script","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/workflow-launch-records-carry-a-hidden-script-digest","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Workflow launch records can now carry a fingerprint of a hidden script\n\nWhen it reads a workflow launch record, Claude Code now keeps a SHA-256 fingerprint of a hidden script along with the result\n\n**What**\n\nWhen Claude Code reads the record of a launched workflow, it now picks up a SHA-256 digest of a hidden script and keeps it with the result. A digest is a short fingerprint that changes if the script changes. Before, Claude Code only handled records for a workflow's result, its start and its failure.\n\n**Why**\n\nThis gives Claude Code what it would need to check that a launched workflow ran the script it was meant to run.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}