ktm agents

Agents — infrastructure health, capacity, and runtime feature control

Usage

ktm agents [flags]

Subcommands

Details

Manage agents (the hardware/software that runs resources). Operator-scoped.

Three agent types: cellular GSM gateways with SIM card slots ethernet Standalone web agents (no slots, capacity = max parallel tests) smartphone Phone hubs with connected smartphones

Every command below identifies an agent with --agent, which accepts either the agent's hostname or its UUID — the HOSTNAME and UUID columns of 'agents list'.

Common tasks: ktm agents list --operator <slug> --type smartphone → fleet health ktm agents get --agent <hostname|uuid> → one agent in detail, with slots ktm agents adapters list --agent <hostname|uuid> → its runtime-controllable features ktm agents adapters get <name> --agent <hostname|uuid> → what that feature exposes: settings, types, what is writable ktm agents adapters set <name> KEY=VALUE --agent <hostname|uuid> [--resource <serial>] → change a setting, for the agent or one phone ktm agents adapters enable|disable <name> --agent <hostname|uuid> → start/stop a feature, no agent restart ktm agents reboot --agent <hostname|uuid> --confirm → reboot an agent ktm agents maintenance --agent <hostname|uuid> --enable --confirm → stop scheduling tests on it

Runtime adapter changes — toggles and settings alike (e.g. the ADB bridge, adapter name adb_bridge) — are ephemeral: after an agent restart, the agent's own configuration decides again. For the ADB bridge, 'ktm adb status|enable|disable' are the phone-centric shortcuts.

Use 'resources list' for product-scoped device info instead.

Related

• ktm agents list
• ktm agents get
• ktm agents adapters list
• ktm agents adapters get
• ktm agents adapters set
• ktm agents adapters
• ktm agents reboot
• ktm agents maintenance

What's next?