Loopsy, a way for terminals and AI agents on different machines to talk
I've always had the urge to have my two macbooks communicate. Having one idle while working on the other felt like underutilization of resources. So I built Loopsy. Initially the goal was to do file transfer via local network, and then came running commands. I then tried running coding agents from one machine to the other, and it worked. Later I figured there should be a better way to continue my claude sessions remotely on my phone from the gym. So I did a cloudflare worker that connects to my local machine. I just need to ensure the laptop is plugged in. I know I might be reinventing the…
Loopsy, a way for terminals and AI agents on different machines to talk launched on May 1, 2026 with 58 votes, #733 of 20,538 launches that month and more than 95% of that year's launches.
In plain words
Loopsy enables terminals and AI agents to communicate across different machines over local networks and remote connections. It supports file transfers, remote command execution, and running AI coding agents between computers. Users can also continue Claude sessions remotely through a Cloudflare worker integration, allowing access from mobile devices. The tool is designed for developers who want to utilize multiple machines more efficiently and maintain continuity in their AI workflows across devices.
written from the facts on this page · September 2026
From the sources
Cross-machine AI agent communication, plus a mobile app to control any terminal on your machine. - leox255/loopsy
In the maker’s words, at launch
I've always had the urge to have my two macbooks communicate. Having one idle while working on the other felt like underutilization of resources. So I built Loopsy. Initially the goal was to do file transfer via local network, and then came running commands. I then tried running coding agents from one machine to the…
Does a similar job
all alternatives →
Humans in the LoopJan 2026 · clawsyndicate.ai · ▲461A free community to talk all-things-agentic-coding-AI
ClaudyMay 2026 · claudy.markg.app · ▲163A proper home for Claude Code — multi-session, multi-account
Parallel CodeMar 2026 · parallelcode.app · ▲159I kept running into a structural problem with AI coding tools. You try one agent. It makes changes. You try another. Now you're manually diffing branches and cleaning up experimental commits. The tools are powerful, but the workflow isn’t designed for comparison. So I built Parallel Code. It runs Claude Code, Codex, and Gemini CLI natively (no API wrapper, no feature abstraction), but isolates each agent in: its own terminal its own Git worktree its own feature branch The workflow becomes: Spawn N worktrees Assign one AI agent per worktree Let them implement independently Compare diffs Merge…
TermlyNov 2025 · termly.dev · ▲82Hey HN! I'm one of the developers of Termly. Problem: I love using Claude Code for development, but being chained to my laptop all day wasn't working. SSH + terminal emulators felt clunky for interactive AI coding sessions. Solution: Built a WebSocket relay that mirrors your AI coding session to mobile with zero-knowledge E2E encryption. How it works: 1. npm install -g @termly-dev/cli 2. termly start (wraps your AI tool) 3. Scan QR code with mobile app 4. Your session syncs in real-time, encrypted end-to-end Tech stack: • Open source CLI (MIT licensed) - inspect the code yourself •…
Skill that lets Claude Code/Codex spin up VMs and GPUsFeb 2026 · cloudrouter.dev · ▲138I've been working on CloudRouter, a skill + CLI that gives coding agents like Claude Code and Codex the ability to start cloud VMs and GPUs. When an agent writes code, it usually needs to start a dev server, run tests, open a browser to verify its work. Today that all happens on your local machine. This works fine for a single task, but the agent is sharing your computer: your ports, RAM, screen. If you run multiple agents in parallel, it gets a bit chaotic. Docker helps with isolation, but it still uses your machine's resources, and doesn't give the agent a browser, a desktop, or a GPU to…
A local merge queue for parallel Claude Code agentsJul 2026 · github.com · ▲42I have been pushing up to 90 commits a day on a MacBook Air via 4-5 parallel agents. As you can imagine when all the agents try to build, test and run dev servers on an 8GB machine it is the fast lane to a force quit and restart. I also did not want to pay the CI minutes on 90 pushes a day. So I designed a local merge queue to have all commits land one at a time and fully tested. Hopefully this helps other folks with more modest machines. Appreciate any feedback.
More ai this month
the category →
Paintings by AI models: programs run through a simulation of oil paint.
AI · 22d ago · stillwet.art
FastRouter.ai▲364Route requests to the right LLM for cost, latency & quality
AI · 23d ago · fastrouter.ai
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, May 2026
the whole month →
Parallel agents, diff reviewer, and multi-model comparisons
Dev tools · May 2026 · kilo.ai
Hey HN, Henry here from Cactus. We open-sourced Needle, a 26M parameter function-calling (tool use) model. It runs at 6000 tok/s prefill and 1200 tok/s decode on consumer devices. We were always frustrated by the little effort made towards building agentic models that run on budget phones, so we conducted investigations that led to an observation: agentic experiences are built upon tool calling, and massive models are overkill for it. Tool calling is fundamentally retrieval-and-assembly (match query to tool name, extract argument values, emit JSON), not reasoning. Cross-attention…
Life & fun · May 2026 · github.com
🌱 Private, quiet space for thinking. Simple app for .md files. - zakirullin/files.md
Dev tools · May 2026 · github.com