Agent Fleet and Agent Detail

An agent is the runtime installed on a machine you develop or operate on, and in VibeControls it is the unit everything else hangs from. This concept covers the two views a person moves between constantly: the list of every agent in the workspace, and the page for a single agent where its real state lives.

The problem is visibility at two scales. Across a fleet you want to know quickly which agents answered recently and which did not, without reading a wall of text. Inside one agent you want considerably more, because an agent that reports as connected can still be running a degraded plugin, holding stale sessions or filling its log with errors. The illustrated design separates those scales rather than compromising with one crowded table.

The landing illustration shows the agents view as a grid of cards, with a count of how many agents are online, a refresh control and an action to add another. A short banner explains what agents actually do. A search field, a grid and list toggle, and filters for status, platform and tag sit above the cards. Each card carries the agent name, its host, a status pill, how long ago it was last seen, the machine architecture, a truncated connection URL and an overflow menu, so the fleet reads as a set of comparable tiles.

The agent detail illustration opens one of those cards. The header repeats the agent name with an enabled badge, a version badge and the host name, and offers a reconnect action. A wide tab row divides the agent into overview, profiles, security, sessions, plugins, logs, connection log, projects, notes, backup and maintenance, with counts on the tabs that hold items. The plugins tab is shown, split into installed, available and interface plugins, with a search field and a refresh control above a list of plugin rows.

What the plugin list demonstrates is the governance idea behind the product: each row carries a name, a version and one or two state pills, so an update that is waiting, a plugin that is degraded, one that is disconnected and one that is erroring are all legible at a glance. Selection checkboxes on each row imply acting on several plugins at once, which connects this surface to the wider fleet rollout and automation parts of VibeControls.