{"version":"2.1.248","anchor":"a-separate-remote-tool-channel-for-working-copy-sync","canonical_anchor":"a-separate-remote-tool-channel-for-working-copy-sync","heading":"A separate remote tool channel for working-copy sync","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/a-separate-remote-tool-channel-for-working-copy-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### A separate remote tool channel for working-copy sync\n\nA third remote tool channel exists holding just a working-copy sync tool.\n\n**What**\n\nRemote hosts gain a third tool category next to served and passthrough tools, currently containing exactly one entry, `sync_files`, with its own transport call carrying its own deadline, cancellation and timeout. Results can carry a directory-sync field that becomes a session note, and the tool-use display learns a `sync` action shown as \"sync working copy\".\n\n**Details**\n\n- The new call path rejects anything not in the fixed one-item set.\n- The directory-sync field is read from either the structured result content or the result metadata.\n\n**Evidence**\n\n`callPlumbing: not a plumbing tool`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}