---
title: "ListRunnerAgentExecutions"
method: POST
path: "/gitpod.v1.RunnerInteractionService/ListRunnerAgentExecutions"
tags: ["gitpod.v1.RunnerInteractionService"]
---

# ListRunnerAgentExecutions

`POST /gitpod.v1.RunnerInteractionService/ListRunnerAgentExecutions`

## Query parameters

- `pageSize` integer
- `token` string

## Request body

- GitpodV1ListRunnerAgentExecutionsRequest
  - `bigPagination` GitpodV1BigPaginationRequest — Do not use this in user facing APIs unless you have a good reason for that
    - `pageSize` integer — Page size is the maximum number of results to retrieve per page. Defaults to 25. Maximum 10000.
    - `token` string — Token for the next set of results that was returned as next_token of a PaginationResponse
  - `filter` GitpodV1ListRunnerAgentExecutionsRequestFilter
    - `activeOnly` boolean — When true, only return agent executions that require processing. Excludes executions where phase is terminal (stopped/waiting_for_input) and spec.session matches status.session (no new user input).
    - `agentExecutionIds` string[] — When set, only return agent executions matching these IDs.
    - `idsOnly` boolean — When true, return only execution IDs without full content (no spec, status, metadata, or access token).
    - `shardIds` integer[] — Optional shard filter. When set, only return agent executions whose ShardOf(id) is in this set. Used by horizontally-scaled runner replicas to fetch only the resources they own. Values must be in [0, 64).
  - `pagination` GitpodV1PaginationRequest
    - `pageSize` integer — Page size is the maximum number of results to retrieve per page. Defaults to 25. Maximum 100.
    - `token` string — Token for the next set of results that was returned as next_token of a PaginationResponse
  - `runnerId` string, uuid
  - `tokenPresence` 'RUNNER_AGENT_EXECUTION_TOKEN_PRESENCE_UNSPECIFIED' | 'RUNNER_AGENT_EXECUTION_TOKEN_PRESENCE_PRESENT' | 'RUNNER_AGENT_EXECUTION_TOKEN_PRESENCE_OMIT'

## Response `200`

Success

- GitpodV1ListRunnerAgentExecutionsResponse
  - `agentExecutions` GitpodV1RunnerAgentExecution[] — The agent ListRunnerAgentExecutionsRequest on the runner
    - `actorAccessToken` string
    - `agentExecution` GitpodV1AgentExecution
      - `id` string — ID is a unique identifier of this agent run. No other agent run with the same name must be managed by this agent manager
      - `metadata` GitpodV1AgentExecutionMetadata
        - `annotations` object — annotations are key-value pairs for tracking external context.
        - `createdAt` string, date-time — A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime() ) to obtain a formatter capable of generating timestamps in this format.
        - `creator` GitpodV1Subject
          - `id` string, uuid — id is the UUID of the subject
          - `principal` 'PRINCIPAL_UNSPECIFIED' | 'PRINCIPAL_ACCOUNT' | 'PRINCIPAL_USER' | 'PRINCIPAL_RUNNER' | 'PRINCIPAL_ENVIRONMENT' | 'PRINCIPAL_SERVICE_ACCOUNT' | 'PRINCIPAL_RUNNER_MANAGER'
        - `description` string
        - `name` string
        - `role` 'AGENT_EXECUTION_ROLE_UNSPECIFIED' | 'AGENT_EXECUTION_ROLE_DEFAULT' | 'AGENT_EXECUTION_ROLE_WORKFLOW' — AgentExecutionRole represents the role of an agent execution
        - `sessionId` string — session_id is the ID of the session this agent execution belongs to.
        - `updatedAt` string, date-time — A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime() ) to obtain a formatter capable of generating timestamps in this format.
        - `workflowActionId` string, uuid, nullable — workflow_action_id is set when this agent execution was created as part of a workflow. Used to correlate agent executions with their parent workflow execution action.
      - `spec` GitpodV1AgentExecutionSpec — unresolved $ref
      - `status` GitpodV1AgentExecutionStatus — unresolved $ref
  - `pagination` GitpodV1PaginationResponse
    - `nextToken` string — Token passed for retrieving the next set of results. Empty if there are no more results

## Other responses

- `default` — Error

## Changes

> 18 revisions in range; 1 could not be searched.

- **2026-04-02** `dabc0ff98cd7` — 3 warning, 8 info
  - added the new `SUPPORTED_MODEL_HAIKU_4_5` enum value to the `agentExecutions/items/agentExecution/status/supportedModel` response property for the response status `200`
  - added the new `SUPPORTED_MODEL_SONNET_4_6` enum value to the `agentExecutions/items/agentExecution/status/supportedModel` response property for the response status `200`
  - added the new `SUPPORTED_MODEL_SONNET_4_6_EXTENDED` enum value to the `agentExecutions/items/agentExecution/status/supportedModel` response property for the response status `200`
  - added the new optional request property `filter`
  - …7 more
- **2026-02-11** `b97dcde84128` — 2 warning, 2 info
  - added the new `SUPPORTED_MODEL_OPUS_4_6` enum value to the `agentExecutions/items/agentExecution/status/supportedModel` response property for the response status `200`
  - added the new `SUPPORTED_MODEL_OPUS_4_6_EXTENDED` enum value to the `agentExecutions/items/agentExecution/status/supportedModel` response property for the response status `200`
  - added the optional property `agentExecutions/items/agentExecution/metadata/annotations` to the response with the `200` status
  - added the optional property `agentExecutions/items/agentExecution/status/mcpIntegrationStatuses` to the response with the `200` status
- …earlier changes not shown

[Full history](https://skmtc.dev/gitpod-io/apis/gitpod-v1/changes/gitpod.v1.RunnerInteractionService/ListRunnerAgentExecutions/post.md)

---

[API](https://skmtc.dev/gitpod-io/apis/gitpod-v1.md) · [All operations](https://skmtc.dev/gitpod-io/apis/gitpod-v1/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/gitpod-io/gitpod-v1/revisions/44d50c2ac284/schema)
