> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Workspace environments

> Inspect the runtime containers agents in a Guild workspace have used: their status, events, and logs. Download setup logs and destroy runtimes.

The **Environments** page lists the runtimes agents in this workspace have run in. A runtime is a container built from a [runtime environment](https://docs.guild.ai/platform/environments.md), where agents get tools like filesystem access, git, and coding CLIs. Open the workspace and click **Environments** under **Setup**.

This page shows runtimes only. To create or edit the environments they're built from, open **Environments** in the account's **Access & setup** section. See [Runtime environments](https://docs.guild.ai/platform/environments.md).

The list shows each runtime's **Status** (**RUNNING**, **STARTING**, **ERRORED**, or **DESTROYED**), **Started at**, **Destroyed at**, **Duration**, and **Created by**, the agent or person that started it. Filter it with **All runtimes**, **Active runtimes**, or **Inactive runtimes**. Runtimes appear as agents use them; you don't create them here.

Select a runtime to open its detail page:

| Card | What it shows |
| - | - |
| **Overview** | **Runtime ID**, **Created By**, the **Environment** it was built from (linked), **Started at**, **Destroyed at**, and **Base Path**. When a runtime is locked to one session, **Locked Session** names it. Only that session can use the runtime until you unlock it. |
| **Events** | One row per command or call the runtime handled, with **Type**, **Status**, and **Completed At**. Select a row to see its details, such as a command's return code and output, or a call's request and response. |
| **Logs** | The runtime's log lines, with **Logged at**, **Log level**, and **Log line**. |

Where a runtime captured the full output of its setup script, the detail page shows a **Setup Logs** field and download buttons in the **Logs** card header, **Download stdout** and **Download stderr**. A runtime whose setup succeeded shows no buttons. The same downloads are offered on the failure event in the session view. See [Setup log downloads](https://docs.guild.ai/platform/sessions.md#setup-log-downloads).

Click **Destroy** to permanently remove a runtime and its container. This can't be undone.

## Related pages

* [Runtime environments](https://docs.guild.ai/platform/environments.md) for base images, setup scripts, and every runtime in the account
* [Sessions](https://docs.guild.ai/platform/sessions.md) for the sessions that used each runtime