---
title: Fleet
description: The cross-tenant agent roll-up at
---

# Fleet



## Purpose

FLEET is the cross-tenant roll-up: every enrolled remote-support agent across all tenants in one table, used to spot which tenants have agents online. To act on one tenant, select it on TENANTS and use the [Agents](/docs/console/agents) view.

Deep link: `ops.useargus.co/#/fleet` (nav group REMOTE SUPPORT).

## What it shows

* A header reading `FLEET (N)` with a summary line: tenants, online, revoked counts.
* A table with columns: AGENT, TENANT, NAME, STATUS (active or revoked, color-coded), CONNECTION (online, stale, or offline), LAST SEEN, and an action column.

Data source: `GET /support/fleet`.

## Actions

* REVOKE on an active agent opens the same destructive step-up modal as the Agents view (type the agent id to confirm, reason required). It is inert until the server-side browser-commands flag is enabled; until then it reports "Browser commands not enabled yet". See the [revoke guide](/docs/remote-support/revoke).

## Matching CLI

```bash
argusctl agent fleet
argusctl support fleet
```

The two spellings hit the same endpoint. See [argusctl agent](/docs/cli/agent) and [argusctl support](/docs/cli/support).

## Notes

* Polled on the 15 second timer with in-place repaint; stale data is kept on a failed refresh.
* Empty state: "No agents enrolled on any tenant yet."


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)