Gesta
People and agents

Manage the agent fleet

Understand connected machines, connection health, integrations, and runtime updates.

The Agents page gives Owners a current inventory of employee machines enrolled in Gesta. Use it to verify onboarding, find machines that need attention, and confirm that supported AI agent integrations are available. On macOS, Codex CLI and Codex Desktop are reported separately.

Read the fleet summary

The summary highlights:

  • Online agents: machines currently reporting to Gesta;
  • Total agents: all machines enrolled in the organization;
  • Human users: employees represented by those machines;
  • Needs attention: machines with a connection or update issue to review.

A machine can remain in the inventory while it is offline. Use the latest heartbeat and recent sessions to distinguish a temporarily idle machine from an onboarding or runtime problem.

Agent fleet
Agent fleetReview fleet totals, connection status, runtime versions, users, adapters, and last-seen times.

Find a machine

Search by hostname, employee, agent integration, or runtime version. Use status filters when you need to:

  • confirm that a newly onboarded employee is connected;
  • find machines that have stopped reporting;
  • identify older runtime versions;
  • verify which machines detect Codex CLI, Codex Desktop, or Claude Code;
  • narrow an incident review to a specific employee or host.

Review machine details

Open a machine to review:

  • employee ownership;
  • hostname and platform;
  • connection status and last seen time;
  • installed runtime version and available update;
  • detected agent integrations;
  • recent sessions.
Agent details
Agent detailsInspect the selected endpoint's version, platform, owner, adapters, health, and recent sessions.

Update a runtime

When a machine needs a manual update, ask the employee to run the latest installation command from the Connect dialog on that machine. Automatic behavior depends on the organization upgrade mode. Then:

  1. start a new supported agent session;
  2. refresh the Agents page;
  3. confirm the expected runtime version;
  4. verify a recent heartbeat and session.

The organization can also choose an upgrade mode in Organization settings.

Investigate a machine that needs attention

Check the following in order:

  1. Is the machine expected to be active?
  2. Is the employee signed in to the intended organization?
  3. Does the runtime process start successfully?
  4. Is the supported AI agent installed and detected?
  5. Does a new session appear after the employee sends a prompt?
  6. Is an update available?

Do not delete or reassign an agent record until you have confirmed the exact machine, its owner, and the expected impact. For connection-specific steps, see Troubleshooting.

Fleet hygiene

Review the fleet regularly to find:

  • machines assigned to inactive members;
  • duplicate or renamed hosts;
  • versions that are no longer current;
  • employees who enrolled but never completed a session;
  • machines that have not reported for an unusual period.

Use fleet status as an operational signal, not as an employee performance score.

On this page