Loopsy, a way for terminals and AI agents on different machines to talk
AgentFreeI'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 f
Capabilities8 decomposed
cross-machine terminal session bridging
Medium confidenceEstablishes bidirectional communication channels between terminal instances running on different machines, allowing stdin/stdout/stderr streams to be transmitted over a network transport layer. Implements a client-server architecture where terminal I/O is serialized into messages and routed through a central coordination point, enabling remote command execution and output streaming without SSH or traditional shell tunneling.
Implements terminal bridging as a lightweight message-passing protocol rather than traditional SSH/RPC, allowing AI agents to coordinate execution without shell access or authentication overhead
Lighter-weight than SSH-based solutions and more flexible than REST APIs for streaming terminal I/O, but lacks encryption and session persistence built-in
ai agent-to-agent command relay
Medium confidenceEnables AI agents running on different machines to send commands and receive responses from each other through a standardized message protocol. Agents register themselves with a central broker, publish their capabilities, and can invoke remote agent functions by name with serialized arguments, implementing a publish-subscribe pattern for agent-to-agent RPC without requiring shared memory or direct network knowledge.
Implements agent-to-agent communication through a broker-based publish-subscribe model rather than direct peer-to-peer connections, allowing agents to remain decoupled and enabling dynamic scaling without topology changes
More flexible than direct HTTP APIs between agents because it decouples topology from communication, but lacks the observability and transaction guarantees of message queues like RabbitMQ or Kafka
terminal output streaming with real-time synchronization
Medium confidenceCaptures terminal output (stdout/stderr) from a source machine and streams it in real-time to one or more destination terminals on different machines, maintaining character-level synchronization and preserving terminal control sequences. Uses a buffering strategy to handle network jitter and implements backpressure mechanisms to prevent buffer overflow when destination terminals lag behind source output rate.
Implements character-level streaming with backpressure handling rather than line-buffered or batch transmission, enabling true real-time monitoring of high-frequency output without buffering delays
More responsive than traditional log aggregation (ELK, Splunk) for live monitoring because it streams at character granularity, but lacks the indexing and search capabilities of dedicated logging platforms
command execution with environment variable inheritance
Medium confidenceExecutes commands on remote machines while preserving or selectively overriding environment variables from the originating context. Implements environment serialization that captures the caller's environment state, transmits it to the remote machine, and merges it with the remote machine's base environment according to a conflict resolution policy (e.g., caller overrides, remote overrides, or merge with precedence rules).
Implements explicit environment serialization and transmission rather than relying on shell login scripts or SSH agent forwarding, enabling deterministic environment replication across heterogeneous machines
More explicit and debuggable than SSH environment forwarding because environment state is visible and serialized, but requires more setup than simple SSH_AGENT forwarding
persistent connection pooling with automatic reconnection
Medium confidenceMaintains a pool of persistent TCP/UDP connections between machines with automatic detection of connection failures and transparent reconnection without losing queued messages. Implements exponential backoff for reconnection attempts, message buffering during disconnection periods, and a configurable maximum buffer size to prevent unbounded memory growth. Reconnected clients automatically resync state with the server to ensure consistency.
Implements transparent reconnection with message buffering at the connection pool level rather than requiring application-level retry logic, enabling resilience without explicit error handling in client code
More transparent than manual retry loops but less robust than message queues because buffered messages are not persisted to disk and can be lost on process crash
multi-machine command chaining with output piping
Medium confidenceEnables sequential execution of commands across multiple machines where the stdout of a command on one machine is piped as stdin to a command on another machine. Implements a pipeline orchestrator that manages data flow between machines, handles backpressure when downstream commands are slow, and provides error propagation so that failures in any stage halt the pipeline. Supports both linear pipelines (A→B→C) and fan-out patterns (A→B, A→C).
Implements cross-machine piping through a centralized pipeline orchestrator that manages backpressure and error propagation, rather than relying on direct peer-to-peer connections or message queues
More flexible than shell pipes for distributed execution and simpler than Airflow/Prefect for basic pipelines, but lacks the scheduling, monitoring, and retry capabilities of enterprise orchestration platforms
agent capability registration and discovery
Medium confidenceProvides a registry where AI agents can advertise their capabilities (available commands, input schemas, output schemas) to a central broker, and other agents can query the registry to discover available capabilities without prior knowledge. Implements a schema-based capability definition format (likely JSON Schema or Protocol Buffers) that describes input parameters, output types, and execution constraints. Discovery queries support filtering by capability name, tags, or required input types.
Implements capability discovery through a centralized schema registry rather than hardcoded agent addresses or DNS-based service discovery, enabling dynamic agent networks with explicit capability contracts
More flexible than static configuration files and more explicit than DNS-based discovery, but requires schema maintenance and doesn't provide load balancing or health checking
terminal session state serialization and replay
Medium confidenceCaptures the complete state of a terminal session (command history, environment variables, working directory, output) and serializes it to a portable format that can be replayed on another machine or at a later time. Implements a session log format that includes timestamps for each I/O event, enabling deterministic replay with original timing or accelerated playback. Supports filtering and searching within session logs to extract specific commands or output segments.
Implements session capture at the terminal I/O level with timestamp preservation, enabling deterministic replay with original timing rather than just storing command history
More detailed than shell history files because it captures output and timing, but less comprehensive than full system call tracing and requires more storage
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Loopsy, a way for terminals and AI agents on different machines to talk, ranked by overlap. Discovered automatically through the match graph.
mcp-interactive-terminal
MCP server that gives AI agents (Claude Code, Cursor, Windsurf) real interactive terminal sessions — REPLs, SSH, databases, Docker, and any interactive CLI with clean output via xterm-headless, smart completion detection, and 7-layer security. Install: npx -y mcp-interactive-terminal
Agent Multiplexer – manage Claude Code via tmux
Show HN: Agent Multiplexer – manage Claude Code via tmux
open-terminal
A computer you can curl ⚡
AgentsMesh
The AI Agent Workforce Platform — where teams scale beyond headcount. Give every team member an AI agent squad.
agent-of-empires
Manage multiple Claude Code, OpenCode agents from either TUI or Web for easy access on mobile. Also supports Mistral Vibe, Codex CLI, Gemini CLI, Pi.dev, Copilot CLI, Factory Droid Coding. Uses tmux and git worktrees.
Instrukt
Terminal env for interacting with with AI agents
Best For
- ✓DevOps engineers managing distributed systems without SSH access
- ✓AI agent orchestrators coordinating execution across multiple compute nodes
- ✓Teams building decentralized terminal-based workflows
- ✓Teams building multi-agent AI systems across distributed infrastructure
- ✓Researchers experimenting with agent collaboration and task decomposition
- ✓Organizations with specialized AI agents deployed on different hardware (GPU clusters, edge devices)
- ✓System administrators monitoring distributed deployments
- ✓DevOps teams running shared terminal sessions for incident response
Known Limitations
- ⚠No built-in encryption — requires external TLS/VPN for secure transmission over untrusted networks
- ⚠Latency overhead from message serialization/deserialization on each I/O operation
- ⚠No session persistence — connection loss requires manual reconnection and state recovery
- ⚠Limited to text-based I/O — binary streams and interactive terminal features (colors, formatting) may degrade
- ⚠No built-in request/response timeout handling — long-running agent tasks may cause caller to hang indefinitely
- ⚠Message ordering not guaranteed across multiple relay hops — complex workflows may require explicit sequencing
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
Show HN: Loopsy, a way for terminals and AI agents on different machines to talk
Categories
Alternatives to Loopsy, a way for terminals and AI agents on different machines to talk
Search the Supabase docs for up-to-date guidance and troubleshoot errors quickly. Manage organizations, projects, databases, and Edge Functions, including migrations, SQL, logs, advisors, keys, and type generation, in one flow. Create and manage development branches to iterate safely, confirm costs
Compare →Are you the builder of Loopsy, a way for terminals and AI agents on different machines to talk?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →