From a336f47dd5c31b2ac4043670f1a751914bf2476d Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Tue, 20 Oct 2026 08:10:52 +0000
Subject: [PATCH] docs: correct the initial SSH workspace directory

The integration guide suggested SSH shells might start outside the primary workspace. State that interactive SSH starts in the sandbox workspace while editor folder pickers can choose another location.
---
 content/manuals/ai/sandboxes/integrations/_index.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/manuals/ai/sandboxes/integrations/_index.md b/content/manuals/ai/sandboxes/integrations/_index.md
index ccde9150e4..86624b79a9 100644
--- a/content/manuals/ai/sandboxes/integrations/_index.md
+++ b/content/manuals/ai/sandboxes/integrations/_index.md
@@ -120,10 +120,10 @@ $ ssh demo.sbx
 
 Connecting an app to a sandbox selects the remote environment, but it might not
 open the primary workspace automatically. The initial folder depends on the
-client. A remote folder picker might open at the sandbox user's home directory,
-`/home/agent`, while an interactive `ssh` shell might start in
-`/home/agent/workspace`. Select the intended folder explicitly instead of
-relying on the initial location.
+client. An interactive SSH shell starts in the sandbox workspace, matching
+`sbx exec`. An editor's remote folder picker might open at the sandbox user's
+home directory, `/home/agent`. Select the intended folder explicitly in the
+editor instead of relying on its initial location.
 
 For a sandbox with a primary workspace, each workspace path appears inside the
 sandbox at the same absolute path as on the host. For example, if you pass