Source: https://harnsy.dev/features/machines

> Laptop, server, production, staging. Each environment has its own agent and its own access. It’s in every harnsy build; a harnsy Max key turns it on.

# One company across several machines.

Laptop, server, production, staging. Each environment has its own agent and its own access. It’s in every harnsy build; a harnsy Max key turns it on.

Nodes in the dashboard: the master and its members, one channel each. Sample data.

## Many machines, one cluster.

One machine is the main one; the others join it. A member can be your own server, a laptop at home or another person’s machine with their own Claude or Codex login.

### What crosses between machines.

Messages between agents, which travel through the main machine, and the files a machine chooses to share, read-only. If a member joins through the relay, the relay carries the messages encrypted and cannot read them. The main machine also sees each member’s agent names, harness, status and folder. Logins and keys stay on the machine they belong to. Tasks and boards stay on each machine.

Two ways to connect, above.

## Production has its own agent.

Only the agent that lives on production can reach it. Agents on your machine ask it like a colleague: check the database, pull analytics, update staging. In the author’s setup it audits marketing, SEO and site analytics, and a staging agent fixes what a release breaks with a local one.

## Agents on the server, controls on your desk.

Put harnsy on a server where your agents have the models and services they need and a stable network. They keep working while your laptop is closed, and you see their terminals in your own dashboard. The server decides what’s allowed: nothing, watching, or typing too.

## The main machine shares its harnsy Max.

The main machine shares its harnsy Max with the others, as many machines as its key allows.

## Join from the dashboard.

Paste the command the main machine gives you into the other machine’s dashboard; it needs no key of its own. Only a person joins machines.

## An address is machine/agent.

On your machine an agent goes by its name; on another one, by `machine/agent`, e.g. `prod/audit-3f`. The message travels through the main machine and arrives signed the same way, so a reply just works.

## No open ports.

One machine is the main one. The others connect out to it over one connection, so they work behind NAT and firewalls with no router rules.

## A token per machine.

Rights: read, send, manage. Any token can be revoked on its own, and that machine’s connection closes at once.

## An agent without harnsy.

On a machine where you can’t install harnsy, an agent can join as a remote member with a token.

## Open the dashboard from outside.

With harnsy Max, a phone or a laptop away from home opens your dashboard with a passkey, with no password. The guide takes you from the door to the first sign-in.

[Step-by-step guide](https://harnsy.dev/gateway) →

## Server behind HTTPS.

Ready examples for nginx and Caddy put the main machine on a VPS behind port 443 with a certificate.

## Direct, when the main machine can be reached.

Pick it when the main machine has an address the others can reach: a server, a public IP or a forwarded port. The other machines join it over its cluster port. Needs harnsy Max on the main machine; a machine without its own key borrows harnsy Max from the main one, one seat per machine. The link uses TLS by default.

## Hosted relay, when it can’t.

Pick it when the main machine has no address the others can reach, for example at home behind NAT. The main machine and every member connect out to our relay, so nobody opens a port. Needs a harnsy Max key on the main machine; turn it on there with `harnsy debug cluster relay on`. TLS runs between your machines; the relay cannot read what is inside, and sees which machine, when and how much. One main machine can have direct and relay members at once. You can also run a relay of your own.

[How the relay works](https://harnsy.dev/features/relay) →

## Start a project on the other machine.

Another machine of your cluster uses your keys and subscriptions, and you can start a project right on it. The cluster map shows which machine runs what. A project without a remote git, sent to another machine, arrives with its files; harnsy's own data stays at home.

One main machine, two members directly and one through the relay. Sample data.

## Step by step, per case.

The guide on the relay page goes through each case: a home machine as the main one, a colleague’s machine, a server, direct and relay members together, and taking a member out.

[Open the step-by-step guide](https://harnsy.dev/features/relay) →

Sample data.

## What people use it for.

- Other people’s machines.
   A teammate joins with their own machine and their own Claude or Codex login. Each machine has its own harnsy Max key, or borrows one seat from the main machine.
   The main machine sees: agent names, harness, status, folder and messages. Not logins or keys.
- A home machine as the main one.
   The main machine is a laptop or Mac at home with no public address. Your server and other machines join it through the hosted relay (beta): everyone connects out, and nobody opens a port.
   The relay sees: which machine (as a hash), when and how much. It cannot read messages, tokens or keys.
- Servers: staging, production.
   A server joins as a member, directly when the main machine has an address it can reach. The main machine can message its agents and read the files the server shares, read-only.
   The main machine sees the server’s agent names, harness, status and folder, and the files it shares. The server decides what it shares; its login stays on it.

Give an agent production access? Scary.

## With harnsy Max, your machines join into a cluster — one network of agents.

So production gets its own agent, and only it holds the keys: the laptop agent never touches production — it asks.

Howevery machine connects to the main one over a single connection, and agents write to each other at `machine/agent`.

prod/audit-3f

## A key turns it on.

Add a harnsy Max key on the License page to turn it on.

[Apply for a key →](https://harnsy.dev/account)

[What&#39;s in harnsy, and what&#39;s in harnsy Max?](https://harnsy.dev/#faq-max) →

## Limits, honestly

- The channel has run live between Linux and Windows over a LAN. Server terminals in the laptop’s dashboard are built but not yet run between two machines; neither is the queue for when the main machine is down.
- Teams, history and the links graph stay on each machine; messages travel between them.
- Links between machines use TLS by default; a VPN is only needed to reach machines across networks.
- The right to type into a server’s terminal is shell access to that server. Give it only to your own machines.

## Your first team is one prompt away.

Installing takes one sentence to your agent. To run your agents, harnsy drives a terminal: tmux if it is installed, otherwise its own terminal host (on Windows, always its own).

`Install harnsy following https://harnsy.dev/llms.txt`

## Questions

What&#39;s in harnsy, and what&#39;s in harnsy Max?

harnsy itself is free: 1 organization, 2 projects, no limit on agents, one machine. Claude Code, Codex, OpenCode and pi need their own plans or keys, paid to their providers. harnsy Max is the same build with a key: more projects and organizations, access from your phone (beta), several machines as one team, several subscriptions and their usage.

Is it safe?

As safe as the harnesses you already run. harnsy doesn’t run your agents’ commands: they run inside a harness, under its own permissions, which harnsy does not override. harnsy connects Claude Code, Codex and OpenCode and organises how their agents work together; besides starting the harnesses, it itself runs local git and the actions (scripts) that you enable one by one. The dashboard and agent API listen only on your machine; run by hand, the installer asks before each settings change, and the quick setup an agent runs lists every change; what harnsy sends, and when, is listed under “Where does my data go?”. Several machines (harnsy Max) join with tokens you can revoke, over TLS by default.

Where does my data go?

It stays on your machine, in ~/.harnsy. harnsy has no telemetry. Since 0.11 it asks GitHub once a day whether a new release is out (on by default; you can turn it off on the Updates page). The request carries only harnsy’s version: no key, no machine ID; GitHub sees your IP address, as for any web request. harnsy installs nothing until you press “Update”. Apart from that, by default it opens no connection off your machine; what it sends, and when, is below. It talks to your other machines only if you join them into a cluster (harnsy Max).

While a key is installed, harnsy checks it with the license service about once a day, sending the full key, a hash of the machine’s ID (the ID itself never leaves the machine), a random one-time value, the machine’s name in the license panel, the OS and architecture, the harnsy version and its build date. If you enter a code that starts with HRSY-, harnsy sends it to our license service (lic.harnsy.dev) with a hash of this machine’s ID, the name this machine has in harnsy’s license panel (by default the OS and four characters of the hash, never your host name), the OS and architecture, and the harnsy version, and gets your full key back. Right after that it sends the full key with the same details, the harnsy build date and a random one-time value. harnsy does not store the code.

Before you add a key, harnsy goes online only when you use a feature that needs it, for example checking for updates, checking a provider connection, logging in to ChatGPT for Codex, dictation or transcribing a recording, the plugin catalog, or a Telegram, Discord or GitHub connection you add.

The node’s browser (since 0.11.0). If you install it, harnsy downloads the browser and its control package once (about 190 MB) from their public download servers. Then the browser visits the sites your agents open, from your machine and with the profile’s sign-ins; the sites see that the visits come from your machine. What an agent types into a site goes to that site. These visits do not go through us.

Plugin catalog (since 0.11.0). When you open the catalog, install or update a plugin, harnsy fetches the signed catalog and the plugin’s files from plugins.harnsy.dev. While a plugin from the catalog is installed, it also fetches the catalog at start and every 6 hours and switches off any plugin the catalog has withdrawn. The catalog request carries only harnsy’s version: no key, no machine ID, no list of your plugins. Our server in Germany sees your IP address; its log keeps the IP address, the time, the address requested and the program’s name (user-agent) for 7 days. To avoid it, install plugins from a file or a project folder only.

Relay (beta, harnsy Max; since 0.9.0). If you turn on our hosted relay, your node asks the license service once a day for a relay ticket: it proves it holds your license key and gets a signed one-day ticket. The request carries no messages, files, agent or node names. The relay itself only joins encrypted streams; it sees which node (as a hash), the network address it connects from, when and how much, not what is inside.

Phone notifications (since 0.9.0). If you turn them on, your machine sends each notification to the push service of your browser (Google, Apple, Mozilla or Microsoft) as an encrypted message that only your browser can read. The push service sees that a message was sent, when, how large, and the address of your machine, not what is in it. harnsy keeps your browser’s address and keys in its database on your machine, and keeps them, marked as removed, after you remove the device.

The harnsy relay (beta, Max) passes the connection from your phone to your computer without decrypting it, by design; it logs times and byte counts, with the address cut to its network, for up to 14 days.

[Privacy: contact requests](https://harnsy.dev/privacy/contact)

What is harnsy, and what is it not?

harnsy is a developer tool that runs on your computer. It starts and coordinates command-line tools you already installed: Claude Code, Codex, OpenCode and pi. It runs the official CLIs as they are, under your own logins. The keys you add under Connections are sealed on your machine and handed only to the agent started with that connection, in the agent’s environment or its own login file.

It hosts no AI model, resells no AI access and has no credits or tokens: your AI usage is billed by your own provider. It generates no content itself; your agents do the work and you accept the results.

It does not call AI model APIs for your agents’ work. The exceptions: checking a provider connection when you press Check (one small call with your key; for a Claude subscription token, a one-token message), logging in to ChatGPT for Codex, and dictation or transcribing a recording (audio goes to the provider you add).

Your code and prompts do not pass through our servers, except with the hosted relay (beta, harnsy Max; since 0.9.0): it joins encrypted streams between your machines and cannot read what is inside. The only servers of ours it contacts are the license service (activation, the daily key check, releasing a machine, redeeming a short key), the plugin catalog when you open it or install or update a plugin and, once a plugin from the catalog is installed, at start and every 6 hours, to switch off plugins the catalog has withdrawn, and, if you turn on the hosted relay, the relay; it sends no telemetry. Once a day it asks GitHub whether a new release is out (you can turn it off) and installs nothing until you press “Update”. harnsy is not affiliated with Anthropic, OpenAI, OpenCode or the authors of pi; their names are theirs.

All questions →
