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

# Follow Process Stdout

> Replay captured stdout and follow live stdout over Server-Sent Events.

Replay captured stdout and follow new stdout over Server-Sent Events.

## Endpoint

```http theme={null}
GET /api/v1/processes/{pid}/stdout/follow
```

Use `curl -N` or an SSE client so the connection stays open.

## Example Request

```bash theme={null}
curl -N https://<sandbox-id>.sandbox.tensorlake.ai/api/v1/processes/42/stdout/follow \
  -H "Authorization: Bearer $TENSORLAKE_API_KEY"
```

## SSE Events

Tensorlake first replays any captured stdout, then streams live events:

```text theme={null}
event: output
data: {"line":"Processing item 1/10","timestamp":0}

event: output
data: {"line":"Processing item 2/10","timestamp":1710000001000}

event: eof
data: {}
```

Stdout-only events do not include a `stream` field. If you need merged stdout and stderr with stream tags, use [Follow Process Output](/api-reference/v2/processes/follow-output).


## OpenAPI

````yaml get /api/v1/processes/{pid}/stdout/follow
openapi: 3.1.0
info:
  title: Tensorlake API
  description: >-
    Tensorlake Cloud APIs for Sandboxes, Document Ingestion, and Serverless
    Workflows
  license:
    name: ''
  version: 0.1.0
servers:
  - url: https://api.tensorlake.ai/
security:
  - bearerAuth: []
tags:
  - name: Tensorlake Cloud API
    description: >-
      Tensorlake Cloud APIs for Sandboxes, Document Ingestion, and Serverless
      Workflows
paths:
  /api/v1/processes/{pid}/stdout/follow:
    servers:
      - url: https://{identifier}.sandbox.tensorlake.ai
        description: >-
          Example sandbox proxy host for a specific running sandbox. For
          programmatic access, use the sandbox's `ingress_endpoint`.
        variables:
          identifier:
            default: example-sandbox
            description: The sandbox ID or sandbox name.
    parameters:
      - name: pid
        in: path
        description: The operating system PID of the process.
        required: true
        schema:
          type: integer
          format: int32
    get:
      tags:
        - sandbox-processes
      summary: Follow stdout
      description: Replay captured stdout and follow live stdout over Server-Sent Events.
      operationId: sandbox_process_stdout_follow
      responses:
        '200':
          description: Stdout event stream
          content:
            text/event-stream:
              schema:
                type: string
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````