List of CLI arguments received from the daemon client.
Current working directory received from the daemon client.
Environment variables with CLI prefix received from the daemon client.
Stdin text received from the daemon client. This is used for plain text stdin data like replies to prompts.
Length of stdin data received from the daemon client.
The client sends binary stdin data as a multipart request, that contains
a JSON body with stdinLength defined, followed by the raw binary data.
Secret token that proves the daemon client could read the owner-only
daemon PID file (and is therefore the user that owns this daemon).
The daemon generates this token at startup and stores it in the
owner-restricted daemon_pid.json file. The client echoes it back on
every request. This is the authoritative authentication check, since
the user field above is self-asserted and can be spoofed by another
local user (most relevant on Windows, where the named pipe can be
opened by users other than the owner).
The user that initiated the request from the daemon client.
Generated using TypeDoc
Option interface to construct response from daemon client
IDaemonResponse