From aed8b7b4e2561df3cd2f6d53a11b988da37c2780 Mon Sep 17 00:00:00 2001 From: examon Date: Wed, 26 Aug 2026 21:15:19 +0000 Subject: [PATCH] docs: remove false 30-minute idle timeout claim from deployment guides The Limitations tables in docs/setup/scaling.md and docs/setup/backend-services.md state that the CLI automatically cleans up sessions after 30 minutes of inactivity. There is no such timeout: idle sessions are cleaned up only when a positive --session-idle-timeout is configured on the server, and nothing is configured by default. Replace both rows with the opt-in framing already used by docs/features/session-persistence.md. Both guides describe connecting to a separately launched CLI server, where the SDK-side sessionIdleTimeoutSeconds option is documented as ignored, so the rows point at the --session-idle-timeout server flag instead. --- docs/setup/backend-services.md | 2 +- docs/setup/scaling.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/setup/backend-services.md b/docs/setup/backend-services.md index 7f1da36e82..b7b288bb8f 100644 --- a/docs/setup/backend-services.md +++ b/docs/setup/backend-services.md @@ -540,7 +540,7 @@ setInterval(() => cleanupSessions(24 * 60 * 60 * 1000), 60 * 60 * 1000); | **Single CLI server = single point of failure** | See [Scaling guide](./scaling.md) for HA patterns | | **No built-in auth between SDK and CLI** | Secure the network path (same host, VPC, etc.) | | **Session state on local disk** | Mount persistent storage for container restarts | -| **30-minute idle timeout** | Sessions without activity are auto-cleaned | +| **No idle timeout by default** | Pass `--session-idle-timeout ` to the CLI server to automatically clean up inactive sessions | ## When to move on diff --git a/docs/setup/scaling.md b/docs/setup/scaling.md index c4a7a0953f..acf82bdb26 100644 --- a/docs/setup/scaling.md +++ b/docs/setup/scaling.md @@ -626,7 +626,7 @@ flowchart TB | **No built-in session locking** | Implement application-level locking for concurrent access | | **No built-in load balancing** | Use external LB or service mesh | | **Session state is file-based** | Requires shared filesystem for multi-server setups | -| **30-minute idle timeout** | Sessions without activity are auto-cleaned by the CLI | +| **No idle timeout by default** | Pass `--session-idle-timeout ` to the CLI server to automatically clean up inactive sessions | | **CLI is single-process** | Scale by adding more CLI server instances, not threads | ## Next steps