wendy device info
Shows agent version, OS, architecture, GPU, and hardware info for the target device.
wendy device info
Shows agent version, OS, architecture, GPU, and hardware info for the target device.
Usage
wendy device info [flags]Description
wendy device info queries the connected device's agent and prints its version, operating system, CPU architecture, CPU core count, total RAM, GPU presence, and other hardware details. Use this command anywhere device metadata is needed — in scripts, CI pipelines, or interactively.
The output format follows the standard --json / human-readable convention shared across all device commands.
CPU and memory output
Two headline hardware specs are included when the agent reports them. Both are omitted from the human-readable output and the JSON map when the agent cannot read them (older agents or non-Linux hosts), so treat them as optional.
| Field (JSON) | Human-readable label | Description |
|---|---|---|
cpuCount | CPU Cores: | Number of online logical CPU cores. |
memTotalBytes | Memory: | Total physical RAM in bytes; human-readable output shows a formatted size (e.g. 131.9 GB). |
For live CPU and memory utilization, use wendy device top.
GPU output fields
On GPU-capable devices, the following GPU fields are included. Each is omitted from both the human-readable output and the JSON map when the agent does not report it (e.g. non-GPU devices or older agents), so consumers should treat every field as optional.
| Field (JSON) | Human-readable label | Description |
|---|---|---|
gpuVendor | GPU: | GPU vendor (e.g. nvidia, qualcomm); shown as unknown in human-readable output when a GPU is present but the vendor is unreported. |
jetpackVersion | JetPack: | JetPack/L4T version string (Jetson only). |
cudaVersion | CUDA: | CUDA toolkit version (e.g. 12.6). |
gpuArch | GPU Arch: | GPU architecture identifier. Format is vendor-specific (e.g. sm_87 for NVIDIA). |
wendy device info reports static GPU metadata (vendor, architecture, toolkit versions). For live GPU utilization, memory, temperature, and power draw, use wendy device top.
Network output
The output includes the device's network interfaces and their routable IP addresses under a Network: block (human-readable) or a networkInterfaces array (JSON). This is the address to use to reach an app running on the device — the .local hostname does not always resolve on every network.
Loopback, down, and container/virtual bridge interfaces are omitted, as are link-local addresses. The section is absent entirely when the agent cannot enumerate interfaces (e.g. older agents).
| Field (JSON) | Human-readable label | Description |
|---|---|---|
networkInterfaces[].name | (row label) | Interface name (e.g. eth0, wlan0). |
networkInterfaces[].ipAddresses | (row value) | Routable IPv4/IPv6 addresses assigned to the interface. |
Flags
| Flag | Default | Description |
|---|---|---|
--check-updates | false | Check whether a newer agent release is available and include the result in the output. |
--prerelease | false | Include pre-release (nightly) versions when checking for updates. |
Examples
Print device info in human-readable form:
wendy device info --device my-device.localPrint device info as JSON (useful in scripts):
wendy device info --device my-device.local --jsonExtract specific fields with jq:
wendy device info --device my-device.local --json | jq '{osVersion, agentVersion: .version, deviceType, cpuCount, memTotalBytes}'Deprecated alias
wendy device version is a deprecated alias for this command. It remains functional for backward compatibility but is hidden from help output. When invoked in non-JSON mode it prints a deprecation warning to stderr:
Warning: 'wendy device version' is deprecated; use 'wendy device info' instead.No warning is emitted when --json is passed, so existing machine-readable scripts that use wendy device version --json continue to work without noise on stderr.
Migrate any usage of wendy device version to wendy device info.