Terminal: System Monitoring

The terminal service exposes endpoints for inspecting the runtime state of a container instance (CPU, memory, processes, network ports, displays, and daemons) and for actively managing it: sending signals to processes, freezing/resuming workloads, and controlling system power. Use these endpoints to power dashboards, automate cleanup, or correlate resource pressure with running workloads.

All endpoints on this page are scoped to a single container instance. The base URL targets one terminal replica; replace {projectId}, {containerId}, and {server} with values from your environment.

Service Health

`GET /api/v1/terminal/health`

Liveness probe for the terminal service. Returns the standardized 9-field health envelope. Unauthenticated. Always returns HTTP 200 with application/json when the service is responsive.

This endpoint takes no parameters.

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/terminal/health"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.health.check();

{
  "status": "ok",
  "version": "1.4.2",
  "build": "f9c2a1b",
  "uptime_seconds": 86420,
  "started_at": "2025-01-15T10:00:00Z",
  "host": "terminal-1",
  "pid": 142,
  "subsystems": {
    "proc": "ok",
    "net": "ok",
    "power": "ok"
  }
}

System Information

`GET /api/v1/system/resources`

Returns comprehensive system statistics: CPU usage (per-core and aggregate), memory, swap, network interfaces, uptime, and disk usage.

This endpoint takes no parameters.

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/resources"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.getResources();

{
  "hostname": "terminal-1",
  "uptime_seconds": 86420,
  "boot_time": "2025-01-15T10:00:00Z",
  "load_average": [0.42, 0.38, 0.31],
  "cpu": {
    "model": "Intel(R) Xeon(R) Platinum 8358",
    "cores": 8,
    "usage_percent": 12.5,
    "per_core_percent": [10.2, 14.1, 8.7, 11.0, 15.3, 13.2, 12.8, 14.7]
  },
  "memory": {
    "total_bytes": 17179869184,
    "available_bytes": 8589934592,
    "used_bytes": 8589934592,
    "usage_percent": 50.0,
    "buffers_bytes": 268435456,
    "cached_bytes": 1610612736
  },
  "swap": {
    "total_bytes": 4294967296,
    "used_bytes": 0,
    "free_bytes": 4294967296
  },
  "disk": [
    {
      "mount": "/",
      "device": "/dev/sda1",
      "filesystem": "ext4",
      "total_bytes": 536870912000,
      "used_bytes": 214748364800,
      "available_bytes": 322122547200,
      "usage_percent": 40.0
    }
  ],
  "network": [
    {
      "interface": "eth0",
      "is_up": true,
      "rx_bytes": 1073741824,
      "tx_bytes": 536870912,
      "rx_packets": 1000000,
      "tx_packets": 800000,
      "ipv4": ["10.0.0.21"]
    }
  ]
}

`GET /api/v1/system/displays`

Returns information about connected displays, sourced from the host’s external display script. Useful for graphics-aware tooling and remote-desktop dashboards.

This endpoint takes no parameters.

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/displays"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.getDisplayInfo();

[
  {
    "name": "HDMI-1",
    "connected": true,
    "resolution": "3840x2160",
    "refresh_rate_hz": 60,
    "is_primary": true,
    "rotation": 0,
    "scale": 1.0
  },
  {
    "name": "DP-1",
    "connected": false,
    "resolution": null,
    "refresh_rate_hz": null,
    "is_primary": false
  }
]

`GET /api/v1/system/daemon`

Returns the JSON array of daemon programs from the hoody-daemon configuration. Use this to discover long-running background services available on the instance.

This endpoint takes no parameters.

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/daemon"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.getDaemonConfig();

[
  {
    "name": "hoody-watcher",
    "command": "/usr/local/bin/hoody-watcher",
    "args": ["--config", "/etc/hoody/watcher.yaml"],
    "autostart": true,
    "autorestart": true,
    "environment": {
      "HOODY_LOG_LEVEL": "info"
    }
  },
  {
    "name": "hoody-metrics",
    "command": "/usr/local/bin/hoody-metrics",
    "args": ["--port", "9090"],
    "autostart": true,
    "autorestart": true,
    "environment": {}
  }
]

Processes

`GET /api/v1/system/processes`

Returns the array of all running processes, with CPU, memory, and state information. Supports sorting, filtering by name (case-insensitive substring), and limiting result count.

Parameters

Name	In	Type	Required	Description
`sort`	query	string	No	Sort by field. One of `cpu`, `memory`, `pid`, `name`. Default: `pid`.
`limit`	query	integer	No	Maximum number of processes to return. Default: all.
`filter`	query	string	No	Filter by process name (substring match, case-insensitive).

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/processes?sort=cpu&limit=20&filter=node"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.listProcessesIterator({ sort: 'cpu', limit: 20, filter: 'node' });

[
  {
    "pid": 1024,
    "ppid": 1,
    "name": "node",
    "username": "app",
    "cpu_percent": 18.3,
    "memory_percent": 4.2,
    "memory_rss_bytes": 723517440,
    "state": "S",
    "cmdline": "node /srv/app/server.js --port 3000",
    "started_at": "2025-01-15T10:05:21Z",
    "nice": 0,
    "num_threads": 11
  },
  {
    "pid": 1025,
    "ppid": 1024,
    "name": "node",
    "username": "app",
    "cpu_percent": 3.1,
    "memory_percent": 1.8,
    "memory_rss_bytes": 309329920,
    "state": "S",
    "cmdline": "node /srv/app/worker.js",
    "started_at": "2025-01-15T10:05:22Z",
    "nice": 0,
    "num_threads": 5
  }
]

`GET /api/v1/system/processes/{pid}`

Returns detailed information about a specific process: full stats, command line, environment variables, and open files.

Parameters

Name	In	Type	Required	Description
`pid`	path	integer	Yes	Process ID.

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/processes/1024"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.getProcess(1024);

{
  "pid": 1024,
  "ppid": 1,
  "name": "node",
  "username": "app",
  "state": "S",
  "cpu_percent": 18.3,
  "memory_rss_bytes": 723517440,
  "memory_vms_bytes": 2748779069,
  "num_threads": 11,
  "nice": 0,
  "cmdline": ["node", "/srv/app/server.js", "--port", "3000"],
  "started_at": "2025-01-15T10:05:21Z",
  "cwd": "/srv/app",
  "exe": "/usr/local/bin/node",
  "environment": {
    "NODE_ENV": "production",
    "PORT": "3000"
  },
  "open_files": [
    "/srv/app/server.js",
    "/srv/app/package.json",
    "/var/log/app.log"
  ]
}

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Process not found"
}

Error Code	Title	Description	Resolution
`PROCESS_NOT_FOUND`	Process does not exist	The specified PID does not correspond to a running process.	Check PID is valid and process is running.

`POST /api/v1/system/process/signal`

Send a Unix signal to one or more processes. Target by pid (single process) or by name (signals every matching process — case-insensitive comm match, truncated to 15 characters). Supports all standard signals including SIGTERM, SIGKILL, SIGSTOP, SIGCONT, and realtime signals (32..64 on Linux). Pass the signal as a string (SIGTERM, TERM, 15) or as an integer.

Request Body

Field	Type	Required	Description
`pid`	integer	No	Process ID to signal. Mutually exclusive with `name`.
`name`	string	No	Process name to signal — signals ALL matching processes. Mutually exclusive with `pid`.
`signal`	string or integer	No	Signal to send. String form accepts `SIGTERM`, `TERM`, `15`, etc. (with or without `SIG` prefix). Integer form accepts any value in `[0, NSIG)`, including realtime signals `SIGRTMIN`..`SIGRTMAX` (typically 34..64 on Linux), which have no portable string names.
`force`	boolean	No	Shorthand for SIGKILL (`true`) or SIGTERM (`false`) — overrides the `signal` parameter.

curl -X POST "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/process/signal" \
  -H "Content-Type: application/json" \
  -d '{"pid": 1024, "signal": "SIGTERM"}'

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.sendSignal({ pid: 1024, signal: 'SIGTERM' });

{
  "delivered": 1,
  "signal": "SIGTERM",
  "pid": 1024
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Missing target"
}

Error Code	Title	Description	Resolution
`MISSING_TARGET`	Must specify `pid` or `name`	Neither `pid` nor `name` was provided in the request body.	Provide either `pid` or `name` parameter.
`INVALID_SIGNAL`	Invalid signal name	The signal name or integer is not recognized by the kernel.	Use a valid signal (`SIGTERM`, `SIGKILL`, etc.).

{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "Permission denied"
}

Error Code	Title	Description	Resolution
`PERMISSION_DENIED`	No permission to signal process	The kernel returned `EPERM` because the caller is not permitted to signal the target.	Check process ownership.

{
  "statusCode": 405,
  "error": "Method Not Allowed",
  "message": "Method is not POST"
}

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to send signal"
}

Error Code	Title	Description	Resolution
`SIGNAL_FAILED`	Failed to send signal	The signal could not be delivered.	Check process exists.

Process Freeze / Unfreeze

SIGSTOP suspends a process’s entire thread group; SIGCONT resumes it. These endpoints let you pause background workloads (builds, fine-tunes, AI inference) without losing in-memory state, then resume them later.

Target by pid (a single process) or by name (every process whose comm matches case-insensitively). Linux truncates comm to 15 characters; a longer name silently matches nothing. Set include_descendants: true to fan out across the target’s child processes via a one-shot /proc PPID snapshot bounded at 65535 PIDs; the parent is signalled first so a forked child cannot escape, but the operation is best-effort and not atomic. By-name descendant traversal dedupes overlapping subtrees.

`POST /api/v1/system/processes/freeze`

Suspend execution by delivering SIGSTOP to the target process or process tree. Resumed by a matching call to POST /api/v1/system/processes/unfreeze.

Request Body

Field	Type	Required	Description
`pid`	integer	No	Process ID to freeze. Mutually exclusive with `name`. PIDs 1, 2, the server’s own PID, and the server’s parent PID are guarded and return 403.
`name`	string	No	Process name (case-insensitive `comm` match; freezes EVERY matching process). Mutually exclusive with `pid`. Truncated to 15 characters by Linux.
`include_descendants`	boolean	No	When `true`, also freezes every descendant via a `/proc` PPID snapshot (bounded at 65535 PIDs). Default `false`.

curl -X POST "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/processes/freeze" \
  -H "Content-Type: application/json" \
  -d '{"pid": 1024, "include_descendants": true}'

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.freezeProcess({ pid: 1024, include_descendants: true });

{
  "frozen": [1024, 1025, 1102, 1103],
  "skipped": [],
  "include_descendants": true
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Missing target"
}

Error Code	Title	Description	Resolution
`MISSING_TARGET`	Must specify `pid` or `name`	Neither `pid` nor `name` was provided in the request body.	Provide either `pid` or `name` parameter.
`INVALID_PID`	`pid` must be a positive integer within int range	The supplied `pid` was not a positive integer or overflowed the int type.	Contact support.

{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "Permission denied or PID guarded"
}

Error Code	Title	Description	Resolution
`PERMISSION_DENIED`	No permission to freeze process	Either the kernel returned `EPERM` (different UID) or the PID is in the guarded set (init/kthreadd/self/parent).	Either run as the owning UID or target a non-guarded PID.

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Process not found"
}

Error Code	Title	Description	Resolution
`PROCESS_NOT_FOUND`	No process matching `pid`/`name`	The supplied selector did not match any running process.	Verify the target PID or process name.

{
  "statusCode": 405,
  "error": "Method Not Allowed",
  "message": "Method is not POST"
}

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to freeze process"
}

Error Code	Title	Description	Resolution
`FREEZE_FAILED`	Failed to freeze process	The `SIGSTOP` could not be delivered to one or more targets.	Check process exists.
`PROC_SNAPSHOT_OOM`	`/proc` snapshot exhausted memory; transient	The PPID snapshot ran out of memory while resolving descendants.	Contact support.
`PROC_TABLE_TOO_LARGE`	`/proc` PID table exceeds `HT_PID_TABLE_MAX` (65535)	The descendant snapshot bound was exceeded.	Contact support.

`POST /api/v1/system/processes/unfreeze`

Resume execution by delivering SIGCONT. The body schema mirrors /freeze exactly — same pid/name selector and include_descendants option. Calling unfreeze on a process that is already running is harmless: SIGCONT is a no-op for non-stopped processes.

Request Body

Field	Type	Required	Description
`pid`	integer	No	Process ID to unfreeze. Mutually exclusive with `name`. The guarded-PID set (1, 2, self, parent) returns 403.
`name`	string	No	Process name (case-insensitive `comm` match). Mutually exclusive with `pid`. Truncated to 15 characters by Linux.
`include_descendants`	boolean	No	Also unfreeze all descendants via a `/proc` PPID snapshot (bounded at 65535 PIDs). Default `false`. By-name traversal dedupes overlapping subtrees.

curl -X POST "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/processes/unfreeze" \
  -H "Content-Type: application/json" \
  -d '{"pid": 1024, "include_descendants": true}'

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.unfreezeProcess({ pid: 1024, include_descendants: true });

{
  "resumed": [1024, 1025, 1102, 1103],
  "skipped": [],
  "include_descendants": true
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Missing target"
}

Error Code	Title	Description	Resolution
`MISSING_TARGET`	Must specify `pid` or `name`	Neither `pid` nor `name` was provided in the request body.	Provide either `pid` or `name` parameter.
`INVALID_PID`	`pid` must be a positive integer within int range	The supplied `pid` was not a positive integer or overflowed the int type.	Contact support.

{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "Permission denied or PID guarded"
}

Error Code	Title	Description	Resolution
`PERMISSION_DENIED`	No permission to unfreeze process	Either the kernel returned `EPERM` (different UID) or the PID is in the guarded set (init/kthreadd/self/parent).	Either run as the owning UID or target a non-guarded PID.

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Process not found"
}

Error Code	Title	Description	Resolution
`PROCESS_NOT_FOUND`	No process matching `pid`/`name`	The supplied selector did not match any running process.	Verify the target PID or process name.

{
  "statusCode": 405,
  "error": "Method Not Allowed",
  "message": "Method is not POST"
}

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to unfreeze process"
}

Error Code	Title	Description	Resolution
`UNFREEZE_FAILED`	Failed to unfreeze process	The `SIGCONT` could not be delivered to one or more targets.	Check process exists.
`PROC_SNAPSHOT_OOM`	`/proc` snapshot exhausted memory; transient	The PPID snapshot ran out of memory while resolving descendants.	Contact support.
`PROC_TABLE_TOO_LARGE`	`/proc` PID table exceeds `HT_PID_TABLE_MAX` (65535)	The descendant snapshot bound was exceeded.	Contact support.

Network Ports

`GET /api/v1/system/ports`

Returns all listening TCP/UDP ports with owning process information. Supports extensive filtering so you can narrow the result to a specific protocol, user, port, or IP range.

Parameters

Name	In	Type	Required	Description
`protocol`	query	string	No	Filter by protocol: `tcp`, `udp`, or a comma-separated list.
`user`	query	string	No	Filter by user (exact match).
`port`	query	integer	No	Filter by specific port number.
`ip`	query	string	No	Filter by IP address (comma-separated list).
`skip_program`	query	string	No	Exclude specific programs (comma-separated list).
`http_only`	query	boolean	No	Only return HTTP services.
`hoody_only`	query	boolean	No	Only return Hoody Kit services.

curl -X GET "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/ports?protocol=tcp&http_only=true"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.listPortsIterator({ protocol: 'tcp', http_only: true });

[
  {
    "protocol": "tcp",
    "local_address": "0.0.0.0",
    "local_port": 22,
    "remote_address": null,
    "remote_port": null,
    "state": "LISTEN",
    "pid": 812,
    "process_name": "sshd",
    "user": "root"
  },
  {
    "protocol": "tcp",
    "local_address": "127.0.0.1",
    "local_port": 9090,
    "remote_address": null,
    "remote_port": null,
    "state": "LISTEN",
    "pid": 2401,
    "process_name": "hoody-metrics",
    "user": "metrics"
  },
  {
    "protocol": "tcp",
    "local_address": "0.0.0.0",
    "local_port": 3000,
    "remote_address": null,
    "remote_port": null,
    "state": "LISTEN",
    "pid": 1024,
    "process_name": "node",
    "user": "app"
  }
]

Power Management

Both endpoints schedule via shutdown(8), which only schedules in whole minutes — sub-minute delays are rounded up. The actual scheduled delay is reported in the response as effective_minutes. Both require root/sudo; the Linux kernel enforces permission checks.

`POST /api/v1/system/reboot`

Initiate a system reboot. Optionally delay the action by up to 24 hours.

Parameters

Name	In	Type	Required	Description
`delay`	query	integer	No	Delay in seconds before reboot, in the range `0..86400` (default `0` for immediate). The server rounds up to the nearest minute and reports `effective_minutes` in the response.

curl -X POST "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/reboot?delay=60"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.reboot({ delay: 60 });

{
  "scheduled": true,
  "delay_seconds": 60,
  "effective_minutes": 1
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Delay out of range (> 86400)"
}

{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "Reboot requires root privileges"
}

Error Code	Title	Description	Resolution
`ROOT_REQUIRED`	Reboot requires root privileges	The caller is not running as root/sudo.	Run with sudo or as root user.

{
  "statusCode": 405,
  "error": "Method Not Allowed",
  "message": "Method is not POST"
}

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to execute reboot"
}

Error Code	Title	Description	Resolution
`REBOOT_FAILED`	Failed to execute reboot	The `reboot` system call failed.	Check system logs.

`POST /api/v1/system/shutdown`

Initiate a system shutdown. Optionally delay the action by up to 24 hours.

Parameters

Name	In	Type	Required	Description
`delay`	query	integer	No	Delay in seconds before shutdown, in the range `0..86400` (default `0` for immediate). The server rounds up to the nearest minute and reports `effective_minutes` in the response.

curl -X POST "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/system/shutdown?delay=300"

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.system.shutdown({ delay: 300 });

{
  "scheduled": true,
  "delay_seconds": 300,
  "effective_minutes": 5
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Delay out of range (> 86400)"
}

{
  "statusCode": 403,
  "error": "Forbidden",
  "message": "Shutdown requires root privileges"
}

Error Code	Title	Description	Resolution
`ROOT_REQUIRED`	Shutdown requires root privileges	The caller is not running as root/sudo.	Run with sudo or as root user.

{
  "statusCode": 405,
  "error": "Method Not Allowed",
  "message": "Method is not POST"
}

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to execute shutdown"
}

Error Code	Title	Description	Resolution
`SHUTDOWN_FAILED`	Failed to execute shutdown	The `shutdown` system call failed.	Check system logs.

Client Diagnostics Beacon

A terminal client posts its own render/connection health here so the server can correlate client-side stalls (frozen UI, dropped WebSocket, WebGL fallback) with server-side session state.

`POST /api/v1/terminal/state`

Post a client-state envelope for diagnostics correlation. The request body is optional; if omitted, the server just records that the client reached the endpoint.

Request Body

Field	Type	Required	Description
`build_id`	string	No	Frontend build identifier.
`renderer`	string	No	Effective renderer, typically `webgl` or `dom`.
`reason`	string	No	What triggered this beacon (for example, `connection_resumed`, `render_stall`).

curl -X POST "https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com/api/v1/terminal/state" \
  -H "Content-Type: application/json" \
  -d '{"build_id": "web-1.4.2", "renderer": "webgl", "reason": "connection_resumed"}'

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({ baseURL: 'https://{projectId}-{containerId}-terminal-1.{server}.containers.hoody.com', token: process.env.HOODY_TOKEN });

await client.terminal.terminalState.postTerminalState({
  build_id: 'web-1.4.2',
  renderer: 'webgl',
  reason: 'connection_resumed',
});

{}