Remote script. The install step pipes a script from the internet directly into bash, so read it first or pin a trusted version.
Credentials. The remote password you set controls access to the machine, so store it in a password manager and do not share it.
Who it is forA developer with a laptop and a home GPU box who wants agents on both without opening ports or setting up SSH keys.
The problemEach machine has its own agents and terminals, so checking progress means switching between computers.
The outcomeAgents on both machines appear in one app window, and you can open, read, and answer any of them.
What you need first
- macOS or Linux for the desktop app, downloaded from the Harness site
- A terminal on each machine you want to link, with curl available
- A Harness account for the login step
- Claude Code or Codex installed if you want to run those agents
- A GitHub clone of this repo, only for building custom harnesses
Steps
- Download the Harness app for macOS or Linux from the Harness site.
- On the second machine, run
curl -fsSL https://harness.autonomous.ai/cli/install.sh | bash. - Run
harness login, thenharness remote-password set, thenharness starton that machine. - In the app, open Machines and choose Link Machine, then enter the password you set.
- Start a Claude Code or Codex harness on each machine from the app and check that both appear.
Prompt for your agent
In the openharness repo at autonomous-ai/openharness, follow the Get started section to link the machine <machine-name> to the desktop app. Confirm that the daemon runs with `harness start` and that <machine-name> appears under Machines. Report the machine name and the list of harnesses running on it.
Caveat. Harness is in active development and the README does not say which operating systems the CLI supports beyond the desktop app.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page