From 00fae90471f623fc204a6dfea8b7df90243c4161 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Hou=C5=A1ka?= Date: Wed, 4 Nov 2026 23:27:10 +0100 Subject: [PATCH] docs(coding-agent): drop Windows note from RPC shutdown --- packages/coding-agent/docs/rpc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/coding-agent/docs/rpc.md b/packages/coding-agent/docs/rpc.md index 9ee14ee7d..211bfb81c 100644 --- a/packages/coding-agent/docs/rpc.md +++ b/packages/coding-agent/docs/rpc.md @@ -90,7 +90,7 @@ Clients must also handle child-process startup failures, unexpected exits, stder ## Shutdown -Close the child's stdin to request an orderly shutdown. This also works on Windows, where signals cannot be handled and killing the process ends it at once. Pi disposes the active runtime and waits for pending work to finish before exiting, so give it time to exit before killing it. Clients should still handle process signals and unexpected exits. +Close the child's stdin to request an orderly shutdown. Pi disposes the active runtime and waits for pending work to finish before exiting, so give it time to exit before killing it. Clients should still handle process signals and unexpected exits. SIGTERM and SIGHUP also start an orderly shutdown. Once a shutdown has started, from either stdin EOF or a signal, a stdin EOF or a single signal does not interrupt it; a second signal exits at once. Closing stdin and sending SIGTERM together is safe.