v1

latestOpenAPI 3.1.02026-07-2675394318.9 KB
operation

Write to a subprocess's stdin and/or close it

Writes a chunk to the stdin of a live process inside the running instance — spid=1 targets the main process, ≥2 the exec'd children. Requires the process to have been started with stdin.close=false; otherwise its pipe is already at EOF and the call returns 409.

close=true (the default) signals EOF after writing value; an empty value with close=true just closes the pipe. A client that serializes its own requests gets ordered writes; concurrent requests to the same spid are safe but their order is unspecified.

A 504 means the guest write timed out mid-call — the chunk may or may not have been delivered (e.g. the process stopped reading and the pipe is full), so blind retries can duplicate data.

post/operations/{operationId}/subprocesses/{spid}/stdin

Path parameters

operationIdstring uuid required

A UUID string

Example:12345678-9abc-baba-deda-0123456789ab

The ID of the operation

spidinteger required

Spawn id (1 = main process; ≥2 = exec'd children).

Request body

valuestring required

Content to write to stdin (may be empty for a close-only request)

encoding'ascii' | 'base64'

Encoding of the content

closeboolean

true (default) closes stdin (EOF) after writing value — the pre-existing one-shot behavior. false keeps the pipe open so more data can be sent later via POST /operations/{operationId}/subprocesses/{spid}/stdin.

Example request

{
  "value": "aGVsbG8K"
}

Response

Chunk written (and/or stdin closed).