{"version":"2.1.248","anchor":"directory-sync-gains-between-tool-pumps-and-a-post-command-p","canonical_anchor":"directory-sync-gains-between-tool-pumps-and-a-post-command-p","heading":"Directory sync gains between-tool pumps and a post-command pull","tier":"notice","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/directory-sync-gains-between-tool-pumps-and-a-post-command-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Directory sync gains between-tool pumps and a post-command pull\n\nFiles changed by a remote command are pulled back and summarised between tool calls.\n\n**What**\n\nWhen the sync engine supports them, two background pumps now run between tool calls: one pulls down what remote commands changed, one performs uploads that are due. After a command runs on a remote machine, the files it changed are pulled back and summarised in a note such as \"3 files updated here from ...\".\n\n**Details**\n\n- Inside a subagent, pulled files are not written immediately; the write is deferred until the task hands back to the main conversation, and the reminder says so.\n\n**Evidence**\n\n`Directory sync: ${u} sent what that command changed, but those files are written here only after this task hands back to the main conversation`\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}