---
title: "Servers"
id: "2222"
type: "page"
slug: "servers"
published_at: "2026-10-19T23:57:52+00:00"
modified_at: "2026-11-18T17:59:49+00:00"
url: "https://xedant.com/agents/multiagent/docs/servers/"
markdown_url: "https://xedant.com/agents/multiagent/docs/servers.md"
excerpt: "A server is the physical machine hosting your factories. MultiAgent connects to it over SSH…"
---

# Servers

[https://xedant.com/agents/multiagent/docs/servers/.md](https://xedant.com/agents/multiagent/docs/servers/.md)

A server is the physical machine hosting your factories. MultiAgent connects to it over SSH — by password or by private key. If MultiAgent itself is installed on Windows, a local WSL distribution can be used instead of SSH. The connection is stored once per machine — address, port, username, password or key and the jump host — while each [factory](/agents/multiagent/docs/factories)
 stores only a link to its machine.

Several factories live on one machine side by side, and their connection is shared. Credentials are entered once: change the password — and the very next command on any factory of that machine runs with the new password, with no factory to edit one by one.

## The Server List

The **Assets → Servers** section is the table of machines. A row shows the name and address (a record without a name of its own shows just the address), an icon of the connection method, the login and port, the number of factories referencing the machine and the connection state badge: green — connected, red — the connection failed, gray — the machine has not been checked yet. Hover over the badge to read how the last check ended. On the right of the row sit the **“Test Connection”**, **“Edit”** and **“Delete”** actions; clicking the row itself opens the same form.

## Adding a Server

The **“New server”** button opens the connection form. In it, **“Name”** is how the machine is called in the interface. The field is optional: left blank, the machine’s address becomes the name.

Next you choose the connection method: over SSH — then **“Address”**, **“SSH port”**, **“Username”** and **“Authentication”** (a password or a private key) are set; or to a local WSL distribution — this option is offered only where WSL is really available, and then you pick the distribution and no credentials are needed at all.

The password and the private key are stored encrypted and never shown back: the form only shows whether they are set (“Password set”, “Key set”), with a **“Clear”** button beside them. When editing, an empty field means “leave as is”.

Below sits the jump-host (ProxyJump) section. It is needed when a machine is reachable not directly but through another one: **“ProxyJump Host”**, **“ProxyJump Port”** and **“ProxyJump Username”**. An empty host means a direct connection, while an empty username and credentials are taken from the machine itself.

Two records for the same machine cannot be created: if such an address is taken (or, for WSL, such a distribution), the form names the record that holds it.

The same form opens from [adding a factory](/agents/multiagent/docs/factories)
: the machine list has a **“New server…”** item, so a machine can be connected without interrupting the setup. The machine picked when adding a factory is remembered in the browser — next time the form opens on it.

## Connection to the Server

MultiAgent watches the connection itself: every five minutes (and half a minute after start) it sends each machine a short probe. The probe is one per machine, however many factories live on it. The outcome is stored on the machine record, so the state badge updates by itself, without a page reload, on every open surface at once — the servers list, the factories list and the factory header.

The **“Test Connection”** button runs the same probe by hand and shows its progress: report lines appear as they run. The verdict — “Connection successful” or “Connection error” — is written to the same record, so it stays visible after a page reload too.

## One Persistent Connection

Every command, file operation and tunnel to a machine goes over one persistent connection instead of a new one per operation. Pages and polls answer faster, and the machine sees one session instead of dozens. If the SSH service on the machine restarts, the connection restores itself: the next operation simply opens a new connection — no error and no MultiAgent restart needed. After the credentials change, the connection reopens with the new data. It closes when the machine’s last factory or the server record itself is deleted.

The connection is pooled: a 30-second keep-alive holds it through idle periods, tunnels ride the same shared connection, and the one deliberate exception is the parallel server-to-server file copy, whose workers hold their own dedicated connections for throughput.

## Deleting a Server

While at least one factory references the machine, it cannot be deleted: a message with the number of such factories appears instead of the deletion. Delete or move the factories first (or point them at another server on the factory’s General tab) — then the server record can be removed.

## The Reserved Address

The first part of the page address — `servers` — is reserved for this section. The name `servers` cannot be given to an agent, an application or a tool: the service page always stays reachable and no row shadows it (the same rule that protects `factories` and `auth`).

## What Next

- [Hardware](/agents/multiagent/docs/hardware) — how much of these machines’ CPU, memory and disk space is in use: you can see when it is time to add capacity;
- [Factories](/agents/multiagent/docs/factories) — what exactly is deployed on the machines and how to manage it.
