Xedant MultiAgent is the central control panel for a fleet of AI workers — instances of Xedant Agent. It connects to any number of Linux servers over SSH (SSH is the standard way to administer a remote server securely), deploys agents and products on them (Research, Analytics, Data, Proxy, MultiAgent itself, plus chatbots, Telegram, the Test Agent, the News Agent, the Portal Agent and CRM), collects their chats and analytics into one interface, and gives every app its own address on the server through Nginx routing (Nginx is the web server that hands out those addresses).
System requirements: MultiAgent itself is one Docker container (Docker Setup) or the Windows installer (Windows Installation). The servers it manages are Linux (Ubuntu/Debian) with SSH access and root/sudo rights. MultiAgent installs Docker and everything else on those servers by itself.
First Login
Once the container is running, open http://localhost:3990. There are no login and password environment variables to configure — the first user is created with the “Register” button on the login page, and later accounts the same way. Authentication uses JWT tokens valid for 90 days, so you will rarely need to sign in again.
Main Screen
After signing in you land on the main screen with navigation cards for every section of the product. The permanent navigation tree lives in the left sidebar. There are three top-level sections: Servers, Management and Assets. Your servers live under “Servers”, and under each server — its agents and apps: nothing needs adding to the tree by hand, everything appears on its own. A right-click on a row (or the three-dot button) opens the action menu, and its first item is “Open”: for a server it is its home page, for an agent or app its public address. The menu selects the row first, so its page opens right after the menu. The status next to the row updates right there, without leaving the page.
There is no flat page listing all agents: agents are visible under their server’s row, and the fleet’s full list is given by “Registry” in Management. It is convenient to watch the chats of all agents in “Management → Chats”.
- Servers — connecting and setting up servers: SSH, Docker installation, folders and databases, Nginx routing and certificates, the server home page, central login, backups, handing a server to a client;
- Management — the control room for a fleet, once there are many agents. It holds ten screens: “Fleets”, “Registry”, “Chats”, “Decisions”, “Cost”, “Tokens”, “Posture”, “Policies” and “Analytics” as the last item — shared statistics across all agents. The root row of the section itself opens the “Fleet” screen. Details — Management;
- Assets — a folder without a page of its own: clicking it unfolds the list but takes you nowhere. Inside are “Licenses”, “Models”, “Skills”, “Environments”, “Files”, “Tools” and “Accounts”.
From “Assets” it is convenient to hand the same settings out to all agents at once: “Models” and “Skills” are catalogs whose configuration or set of files goes to the agents you pick (the agent’s record with the same name is replaced), and “Environments” are named sets of environment variables. “Files” is for viewing and editing server files together with a terminal, “Tools” is a library of Docker service templates, “Accounts” is for LLM accounts with quotas and balances, and “Licenses” is the agents’ license keys.
When the AGENT_API_URL and AGENT_API_KEY environment variables are set, an Own Agent panel appears at the bottom of the sidebar: a list of active chats with timers and token and cost totals, plus the “Tasks (N)” button — the queue of long jobs with a live counter — and “Chats”. The panel opens from any page and switches between chat and tasks in place. Details in Own Agent and Tasks.
The Typical Path
- Add a server — name, host, SSH port, user, password or private key. The same form sets the deployment slug (default
agents) — the short name that separates this deployment from others on the same machine. When MultiAgent runs on Windows, choose the Local WSL mode instead of SSH — a distribution on this very computer, with no password or key. Details in Servers. - Check the connection — MultiAgent tests SSH and shows the connection status.
- Install Docker — one button, with the output streaming into the interface.
- Add an agent — the Add Agent wizard: pick the type — a standalone agent or a product (Research, Analytics, Data, Proxy, MultiAgent, Chatbot, Telegram, Test, News, Portal, CRM); the name, server, image and port are filled in for you. Details in Agents.
- Deploy the agent or product — MultiAgent generates compose.yml and starts the container on the server. Products deploy together with a linked agent: by default the server’s first standalone agent is used, and if there is none, a new one is created by the same wizard.
- Enable the route — install Nginx from the server’s tab, and the agent immediately gets its own subfolder
{serverHost}/{slug}/on the server. Details in Nginx Routing. - Set up the home page — MultiAgent builds a static card board at the server’s root: agents, apps and tools, while the “QR login” button in the corner opens sign-in from a phone. No separate container and no separate login — Nginx is enough. Details in Server Home Page.
- Turn on central login — the “Authorization” (Authelia) tab on the server page: a visitor signs in once and gets access to every protected app on the server. It needs HTTPS — a local certificate from the Nginx tab, or the server’s public address (an address template like
https://{serverHost}/{slug}works too). Details in Servers. - Open the chats — chats from all agents appear in one shared list. Details in Chats.
Interface Language
The entire interface is in English. The language (English/Russian) is switched in the profile settings and is saved separately for each user.