OpenHarness Lets Developers Run 14 Coding Agents Across Machines at Once
OpenHarness ties every coding agent to persistent tmux sessions across your machines, adds domain-specific specialists for CAD, PCB and robotics, and ships an open-hardware desk device.
- OpenHarness runs Claude Code, Codex, Cursor and 14 other agents in persistent tmux sessions that survive reboots.
- End-to-end encrypted WebRTC relay links all your machines with no SSH, VPN, or open ports required.
- Domain-specific harnesses turn generic agents into specialists for CAD, PCBs, robotics, games and 3D.
- 18 harnesses ship today including Blender, MuJoCo, Godot, Yosys, Manim, Typst and RDKit.
- Open-hardware Harness device: ESP32-S3, 466x466 round AMOLED, full PCB and enclosure files included.
- MIT licensed, macOS primary, Linux in progress, Windows WIP; a Harness account is currently required.
OpenHarness coordinates coding agents across machines
OpenHarness is a new open-source workspace for running multiple coding-agent CLIs across local and remote machines. It combines a desktop app, a background daemon on each host, an end-to-end encrypted relay, persistent tmux sessions, domain-specific tool packages, and an optional desk display. The project addresses a practical limitation of terminal-based agents: long tasks remain tied to individual shells and machines, complicating parallel work and remote supervision.
Sessions that survive disconnects
OpenHarness assigns each agent a persistent tmux session, allowing its process to continue after the desktop app closes or a connection drops. If a reboot stops tmux itself, the daemon recreates the panes and resumes the saved agent sessions.
The daemon integrates with supported agents through their existing transcripts and vendor-provided hooks. The current roster includes Claude Code, Codex, Cursor, OpenCode, Pi, Hermes, Command Code, Devin, Muse Code, Amp, Kilo, Grok Build, Antigravity, and GitHub Copilot. Credentials remain in directories such as ~/.claude and ~/.codex, so each engine continues using its existing subscription or API key.
Remote control through outbound links
Each linked machine runs a daemon that initiates outbound connections. Terminal traffic is encrypted end to end, and the relay forwards ciphertext. When the network permits, the desktop app and daemon establish a direct peer-to-peer connection over WebRTC. The design needs no SSH server, VPN, or public inbound port.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.
Comments
