We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 5 since August 2026, each linked to its source.
circleciWhen inspecting untagged function builds, run `circleci function list --include-pseudo` to include pseudo-versions in each function’s versions. To select or pin one by version, use `--version` or `function add`/`function update` without `--include-pseudo`.[^1][^2]
circleci function list --include-pseudoTo inspect agents for a runner resource class, run `circleci runner fleet get <namespace>/<resource-class>`; use `fleet list` to browse fleets, optionally filtering by organization, namespace, or resource class.
circleci runner fleet list [--org <slug-or-uuid> | --namespace <namespace> | --resource-class <namespace/name-or-id>] [--json] [--jq <jq-expression>]To list deployments across an organization, run `circleci deploy list --org-wide`; add `--limit <number>` to cap results (default 10, or 0 for all).
circleci deploy list --org-wide --limit 50When a CircleCI-managed deployment needs reverting, run `circleci deploy rollback` with the target version, component, and environment; provide the current version with `--from` if you need to assert which deployment is being replaced.
circleci deploy rollback <target-version> --component <component> --environment <environment>When reviewing a repository’s CI configuration, inspect a job’s CPU and memory use against its resource class limits with `circleci job resource-usage get <job-id>`.
circleci job resource-usage get <job-id>