{"version":"2.1.248","anchor":"explanation-to-the-model-when-your-machine-goes-offline-mid-","canonical_anchor":"explanation-to-the-model-when-your-machine-goes-offline-mid-","heading":"Explanation to the model when your machine goes offline mid-upload","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/explanation-to-the-model-when-your-machine-goes-offline-mid-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Explanation to the model when your machine goes offline mid-upload\n\nClaude is told when your local changes didn't upload, plus a token warning about parallel workflows.\n\n**What**\n\nWhen your machine announces newer local changes and then drops off before uploading them, a new message tells the model the current turn is running on stale files and that the changes will arrive in a later turn. A second new warning tells you that dynamic workflows can burn through tokens by running subagents in parallel, pointing at `\/workflows` and `\/config`.\n\n**Details**\n\n- The stale-files note is system-facing, meant to stop the model from acting as if it has the latest edits.\n- The usage warning names `\/workflows` and `\/config` as where to look.\n\n**Evidence**\n\n`the changes arrive at a later turn once the machine is back.`\n\n- Area: Directory Sync\n- Names: `\/workflows`, `\/config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}