Loopsy: Orchestrating Terminals and AI Agents Across Machines

Modern computing environments often involve multiple devices, from powerful workstations to mobile phones, each with untapped potential. Loopsy emerges as a solution to bridge these gaps, offering a novel way for terminals and AI agents to communicate and collaborate across different machines. This tool addresses the common challenge of underutilized resources and the desire for continuous, remote access to ongoing AI sessions, effectively turning a collection of devices into a more unified and powerful computing organism.

The Genesis of Loopsy: Connecting Disparate Machines

The creator of Loopsy was driven by a personal need: to make two MacBooks communicate and leverage their combined resources rather than letting one sit idle. This initial urge evolved from simple file transfers and remote command execution to the more ambitious goal of running coding agents across machines. The vision expanded further to include remote access to ongoing AI sessions, such as Claude, from a mobile device, facilitated by a Cloudflare Worker connecting to a local machine.

This journey highlights a common developer sentiment:

I know I might be reinventing the wheel, but I love that it just works.

This reflects the deep satisfaction of building a practical solution that directly addresses a personal pain point, even if existing alternatives exist. It underscores the value of hands-on experimentation and the creative problem-solving that emerges when developers focus on making something functional and effective.

Beyond Remote Control: A Coherent Organism

Loopsy's approach to inter-machine communication resonates with users seeking more than just traditional remote control. One commenter articulated this distinction:

love this. It feels less like “remote control” and more like turning all your machines + agents into one coherent organism. Curious how you think about the overlap with something like Tailscale, and where you see Loopsy being strictly better or worse.

This perspective points to Loopsy's potential to foster a more integrated and fluid workflow, where machines and AI agents act as extensions of a single, continuous thought process. While tools like Tailscale provide secure network overlays, Loopsy focuses on the application layer, enabling specific interactions like command execution and AI agent orchestration, which might offer a different user experience tailored for distributed agent workflows.

Addressing Technical Considerations and Future Directions

As with any distributed system, several technical considerations and potential enhancements were raised by the community:

Cloudflare Dependence and Self-Hosting

The current implementation leverages Cloudflare Workers for remote access, prompting questions about alternative deployment models:

Dependence on Cloudflare… have you considered making it a service that I could install on my own server?

Offering a self-hosted option would provide greater control and flexibility for users concerned about third-party dependencies or those preferring to run everything within their own infrastructure.

Data Consistency and Concurrency Challenges

A significant challenge in orchestrating agents across multiple machines is managing data consistency and concurrent access, especially when agents are modifying files. One user eloquently described this problem:

The way I see it, having lots of agents that work together across different computers is mostly about a sync-up problem dressed up as something else. Loopsy is a clean tool for sending messages, but I get tripped up on which agent has control of a file at any moment, and what happens when two terminal sessions write to the same file within half a minute. I really need a tool that locks files for editing rather than just one for sending messages. Should the second machine's agent wait its turn until the file is free, or should it create its own branch of the file to merge later? With Loopsy, what we're getting is more like a mailbox system, but in my own setup, the lock would be the right approach in most cases. I have a single rule listed in CLAUDE.md that just reads, "do not modify child project files from parent context." This is because the parent git repository only contains meta-files and automation, and the agent constantly forgets it during sessions, especially when switching machines. After about ten weeks, I added .sync-conflict-* files to my .syncignore.

This highlights the critical need for robust mechanisms to handle file locking, version control, or conflict resolution in multi-agent, multi-machine environments. While Loopsy provides the communication backbone, integrating solutions for state management and concurrency control will be crucial for complex agent workflows.

Security and Platform Expansion

The author noted that End-to-End (E2E) encryption is still a work in progress, which is a vital security feature for any communication tool. Additionally, an iOS app is currently under review, indicating plans for broader platform support. The question of exposing Loopsy as an