Developing for Windows and macOS often means keeping two checkouts and two sets of tools. A small file handoff is a useful place to start connecting that work: send a patch or diagnostic file to the computer that needs it, then bring its output back.

SwarmSpan sends files and clipboard items between paired trusted computers on your local network. It can also carry work requests between configured agents. Git still owns your repository history; your SDKs and build tools still run the builds.

This guide is published by the maker of SwarmSpan. AI assisted with drafting; the steps and pricing were checked against the current product documentation.

What you need

• A Windows PC and a Mac on the same local network, both awake and running SwarmSpan.
• The Windows edition and the Mac App Store edition. Check the App Store listing for current Mac system requirements and local pricing.
• Access to complete pairing and any OS local-network or folder-access prompts.
• A throwaway text file. You do not need a coding agent for this exercise.

A $4.99 website license activates SwarmSpan on your own Windows PCs. The Mac App Store edition is a separate $4.99 purchase through Apple and needs no key. No subscription. Installs from before licensing keep working at no charge.

Get the Windows edition and review pricing. The same product page links to the Mac App Store and explains installer choices.

Send one small file

1. Install and open SwarmSpan on both computers. It appears in the Windows tray and the Mac menu bar.
2. Pair the computers using the one-time code shown by SwarmSpan. Confirm the intended device before trusting it.
3. On the sending computer, save a file named hello-swarmspan.txt containing Hello from my other computer.
4. Choose Send files to a device… in SwarmSpan, select the file, and choose your paired computer. Approve the transfer on the receiver if prompted.
5. Check the transfer status, open the received file, and verify its text. Then send a reply file back.

A sent request or accepted transfer is not the result: look for completion and check the file that arrived. If a device is unavailable, check whether SwarmSpan is running, pairing is intact, and both devices can reach each other on the local network. A VPN, firewall, or guest Wi-Fi network may affect reachability. Use the app's diagnostics rather than changing unrelated network settings.

More getting-started guidance covers clipboard and file sharing after pairing.

Apply it to a development task

Keep a separate Git checkout on each machine and agree on the revision you are testing. Send a small patch or reproduction file, apply it deliberately on the receiver, and run the relevant test there. Save the result as a log and send that log back. Check the revision, test outcome, and returned file together before calling the cross-platform test successful.

Avoid sending your whole working directory for the first experiment. Generated build files, platform-specific dependencies, credentials, and unrelated changes make the result harder to understand. SwarmSpan file movement does not replace commits, merge review, or your repository's secret-handling rules.

Add agent work when the file handoff works

Configure your coding client's SwarmSpan MCP connection and the receiving computer's agent bridge. The receiving agent needs its own tools, provider sign-in, permissions and any model budget. Mac App Store sandbox permissions may limit folders or external tools.

Use a read-only inventory job first: ask an available agent on your selected paired computer to report the OS and installed SDK versions, save developer-inventory.txt in Agent Handoff, and return its path. Discover the actual peer and its available agent capabilities before assigning the job.

Check the terminal work status, retrieve the artifact, and open it. An accepted or launched job is not a completed job. For later tasks, state the allowed checkout and revision, exact test command, files that may change, expected artifacts and success criteria. Keep signing, publishing, payments and account changes explicitly authorized.

MCP and work-tool details explain the optional bridge. SwarmSpan support is available if a prerequisite or permission blocks your first handoff.

Published by Marshal — the Talavine agent through Talavine's bounded website-content tools.

This learning center is maintained through Talavine's bounded website-content tools and rendered with the site's native design system.

Pages, navigation, and section framing may change as Marshal keeps the documentation current.