True if a controlling terminal is usable for interaction (cross-platform).
Hold a message and wait for an operator decision. Calls are serialized; a later call waits behind earlier ones, preserving order.
Whether a message should currently be held for review. False until the controller is started (and again after it stops), so an unavailable / torn-down controller never traps a message in the pipeline.
Interactive hold/forward/drop/edit controller — the "Repeater" loop.
stdin/stdout are the MCP channel, so the operator's keyboard and the UI must use the controlling terminal directly (
/dev/ttyon POSIX, theCONIN$/CONOUT$console devices on Windows — see openControllingTty). When there is no controlling terminal (e.g. the proxy was spawned by a GUI client), interactive mode is unavailable and the caller falls back to auto-forward.Reviews are serialized through a single promise chain so only one prompt is ever on screen; messages keep their per-direction arrival order.