Skip to main content

​
usage

Report Loops GPU capacity, one row per trainer deployment plus a row for each standalone sampler. A summary above the table totals the GPUs in use and scaled to zero. Rows holding no live GPUs (scaled to zero, or in a terminal state) are counted in the summary but hidden unless you pass —all.

​
Options

​
BOOL
Include allocations holding no live GPUs (scaled to zero, or in a terminal state).
​
TEXT
Filter JSON output with a jq expression; implies —output json (or jsonl for streamed commands)
​
BOOL
Report usage across the organization, with each allocation’s owner, instead of only your own.
​
TEXT
default:"text"
Output formatOne of: text, json, jsonl, none
​
TEXT
Use a specific stored profile for this command, overriding BASETEN_PROFILE and the current profile
​
TEXT
Only report allocations owned by this email. Implies —org.
​
BOOL
Enable verbose logging

​
Examples

Report your own Loops GPU usage
Report GPU usage across the organization, including idle allocations
Report GPU usage for one owner

​
Filter output with --jq

Print the total trainer GPUs in use

​
Output

Text mode (--output text): A summary line of trainer and sampler GPU totals, then a table with columns: RUN, OWNER (with —org), BASE MODEL, TRAINER GPU, TRAINER STATUS, SAMPLER GPU, SAMPLER STATUS, CREATED. JSON mode (--output json): payload type cmd.LoopsUsageResult. An object with the GPU summary and one entry per row, each carrying the trainer and sampler allocation and status.