From 4b17d065c1ef327e69e94225e61788f1b30c8055 Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Fri, 11 Sep 2026 12:53:05 +0200
Subject: [PATCH] docs: clarify sandbox background process lifecycle

The Agentic Platform lifecycle guidance did not explicitly cover background processes. Clarify that all processes inside a sandbox stop when the sandbox stops.
---
 content/manuals/agentic-platform/sandboxes.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/manuals/agentic-platform/sandboxes.md b/content/manuals/agentic-platform/sandboxes.md
index 2e10da2ff34..d3dd24e7668 100644
--- a/content/manuals/agentic-platform/sandboxes.md
+++ b/content/manuals/agentic-platform/sandboxes.md
@@ -63,7 +63,8 @@ A sandbox can be running or paused:
 
 When you create a sandbox, set a lifecycle timer from 1 to 24 hours and choose
 what happens when it expires. **Stop** stops the sandbox, while **Delete**
-deletes the sandbox and its files.
+deletes the sandbox and its files. When a sandbox stops, all processes running
+inside it stop too, including background processes.
 
 The sandbox's authentication, tools, access policy, and compute size are fixed
 when the sandbox is created and cannot be changed while it runs.