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

# Remote Plays And Runs

### `DeeplineContext.plays`

Named-play discovery and handle operations from a connected `DeeplineContext`.\
&#x20;Signature: `export type DeeplinePlaysNamespace = { list(): Promise<PlayListItem[]>; get<TInput = Record<string, unknown>, TOutput = unknown>( name: string, ): DeeplineNamedPlay<TInput, TOutput>; };`

### `DeeplineNamedPlay`

Handle to a named play for remote lifecycle operations.

Returned by `DeeplineContext.play` and attached to `DefinedPlay`.
Provides methods to run, inspect, list runs, and publish a play by name.

| Name | Type | Required | Description |
| - | - | -: | - |
| `name` | `string` | Yes | The play's name. |

### `PlayJob`

Handle to a Play execution: inspect status, stream logs, await output, or cancel.
Like `deepline run` and `POST /api/v2/plays/run`, it returns a run id first.
Read completed output through `PlayJob.get()` or the status endpoint's `result` field.
runtime logs in `status().progress.logs` are separate from that output.

| Name | Type | Required | Description |
| - | - | -: | - |
| `id` | `string` | Yes | Temporal workflow ID for this execution. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.