ci.runners.list

List the self-hosted runners registered to this organization

GET /ci/api/runnersIAM ci:DescribeRunnersRead

Credential hashes are never returned. `status` is online, offline or disabled; `lastSeenAt` is the last heartbeat or claim.

Request syntax

GET /ci/api/runners

Response

200 with the runners, by name (the just-in-time runners a Mac or a pool starts per job are left out): id, name, labels, kind (ews-agent or actions-runner), status (as stored), presence (idle, busy, offline or disabled, as of now), capabilities, repositoryId, groupId, poolId, ephemeral, lastSeenAt, registeredAt, capacity (1), vmImage, currentRun and lastRun (each id, repoId, number, workflowName, status, claimedAt, finishedAt, or null).

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow ci:DescribeRunners on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud ci runners list

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ci_runners_list.