{"version":"2.1.296","anchor":"workflow-script-file-is-now-post-processed-and-a-read-length","canonical_anchor":"workflow-script-file-is-now-post-processed-and-a-read-length","heading":"Workflow script files are read to their real length and then processed","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/workflow-script-file-is-now-post-processed-and-a-read-length","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Workflow script files are read to their real length and then processed\n\nWorkflow script files are now read up to the number of bytes actually read, and their text passes through a processing step before use\n\n**Unclear.** It is not clear what the new processing step does to a workflow script's text.\n\n**What**\n\nWhen Claude Code loads a workflow script from a file, two things changed:\n\n- The text is now cut off at the number of bytes actually read from the file, not at a different length.\n\n- The text now goes through a processing step before Claude Code uses it.\n\n**Why**\n\nWorkflow scripts may be read a little differently than before.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}