Endpoints Management

An endpoint is a machine registered in the controller, running the endpoint application, on which steps can run. The Endpoints panel at the bottom left of the Execution tab holds one card per registered machine, and every test that names an endpoint field picks its machines from those cards. This page covers the panel itself; the pages that follow use the endpoints from tests.

The setup guide shows how to install and run the endpoint application and how to add the first endpoint. Here the panel holds the local machine and four others: three added by host name, one Windows, one Linux and one macOS machine, and one added by its IP address:

Endpoint cards

Each card reads from top to bottom: the name it was added by, in a chip, then the other half of its identity, the IP address for a machine added by host name or the host name for a machine added by IP. Below that come the operating system with its icon, the version of the endpoint application, the machine's license state, Licensed once it was activated as the setup guide shows, Secure when the connection uses the controller's security material, and the status button.

The localhost card is the controller's own machine. It is always present, it cannot be removed, and it is where every step runs when a test names no endpoint at all.

The status is the controller's live view of the machine. Ready means the endpoint application answers and can take work. Online means the machine answers a ping but the application does not, and Offline means the machine does not answer at all; the setup guide lists the usual causes of both. While a run holds an endpoint the card reads Busy, and other runs that need the same machine wait for it.

Card actions

Right-click a card to open its actions:

• Info asks the machine for its details and shows them in a dialog.
• Edit reopens the card in the Add Endpoint dialog to change its type, address, port or security.
• Update installs the controller's own version of the endpoint application on the machine and restarts it there, which is how a fleet is kept at one version after a controller upgrade.
• Refresh checks the status again at once instead of waiting for the next poll.
• Revoke License hands the machine's slot back to the account; on a machine without a license the entry reads Activate License instead.
• Remove deletes the card after a confirmation.

Click Info on a card:

The first block is what the controller knows about the card, the machine's license and the date it runs until included. The second is what the machine reported when asked: operating system and build, architecture, processor, the Python running the endpoint application, and its CPU, disk and memory. It is the quickest way to confirm that a machine is the one you think it is.

The Manage dialog

Click Manage in the panel's header to work on every endpoint at once:

Each remote endpoint is a row. The name, type, IP and port cells can be edited in place, and Apply Changes commits every edit together. The handle at the left of a row drags it to another position, which is the order the cards and the endpoint fields list the machines in. The buttons at the right of a row are the card's Refresh and Remove, and the icons beside the version, the license and the status open Update, Revoke License and Info for that row. The SSH column names the way in of an endpoint reached through SSH, a dash for the others.

The check boxes select rows for the two bulk actions. Update Selected installs the controller's version, shown on the button, on every selected machine, and Remove Selected deletes them. Select All ticks every row, and Add Endpoint opens the same dialog as the panel's Add button.

Saving and loading endpoints

Save in the panel's header writes the registered endpoints to a file, and Load reads such a file back. The file records each endpoint's type, host name, IP address, port and security setting, together with the operating system and version last seen. A team can keep one file for its lab and load it on every controller, and it is also the list of machines an AI agent is given when it runs tests.

Collapsing the panel

Click the arrow before the Endpoints title to fold the panel into a single line:

Each chip keeps the endpoint's name, its operating system icon and its status colour, so the state of the lab stays visible while the execution tree takes the room. Click the arrow again to expand the cards.

The next page, Endpoints Config Types, shows how a test declares which of these machines it runs on: a single endpoint, a set of them, or a fan-out that runs the test once per selected machine.