Agent Fleet and Agent Detail

Once agents are installed, the next need is to manage them as a fleet. This concept shows two connected views in VibeControls: the Agents tab of Targets & Agents, which lists every agent in the workspace, and the agent detail page, which gathers everything about a single agent in one place. Together they are designed to replace ad hoc SSH checks with a shared, current picture of which agents exist, whether they are healthy and what they are running.

The agents list illustration presents the fleet as a grid of cards. Each card carries the agent's name and host, the operating system, a status pill such as Active, Degraded or Offline, how recently it was seen, its CPU architecture and the tunnel address it is reachable through. A header summary counts how many agents are online, and search, a grid or list toggle and filters for status, platform and tag make it practical to narrow a large fleet. Refresh and Add Agent actions sit at the top, next to tabs for Targets and the Agent Graph.

The agent detail illustration focuses on one machine. Its header shows the agent's enabled state, version and local hostname, with a Reconnect action for recovering a dropped link. A row of tabs covers overview, profiles, security, sessions, plugins, logs, connection history, bound vibes, notes, backup and maintenance. The Plugins tab is open, separating installed plugins from those available to add and those that contribute interface panels. Each installed plugin, from coding agents to terminal and session providers, shows its version and paired status badges, so a pending update, a degraded integration or an error stands out immediately.

This view is where fleet-level problems become fixable. An offline card on the list leads to the agent page, where connection logs, plugin state and maintenance actions sit side by side, and plugin changes made here feed into the wider plugin marketplace and rollout flows.