docs: remove redundant run workspace paths

Rely on the sbx run current-directory default in direct-mode examples while retaining explicit paths for clone mode.

Author: dvdksn

content/manuals/ai/sandboxes/_index.md

@@ -31,7 +31,7 @@ Then launch an agent in a sandbox:
 
 ```console
 $ cd ~/my-project
-$ sbx run claude .
+$ sbx run claude
 ```
 
 See the [get started guide](get-started.md) for a first-session walkthrough, or

content/manuals/ai/sandboxes/agents/claude-code.md

@@ -20,7 +20,7 @@ $ sbx run claude ~/my-project
 To start Claude with a specific prompt in the current directory:
 
 ```console
-$ sbx run --name my-sandbox claude . -- "Add error handling to the login function"
+$ sbx run --name my-sandbox claude -- "Add error handling to the login function"
 ```
 
 Everything after `--` is passed directly to Claude Code. You can also pipe in a

content/manuals/ai/sandboxes/architecture.md

@@ -63,7 +63,7 @@ To opt out, set
 `DOCKER_SANDBOXES_ENABLE_VIRTIOFS_CACHE=0` when creating the sandbox:
 
 ```console
-$ DOCKER_SANDBOXES_ENABLE_VIRTIOFS_CACHE=0 sbx run <agent> .
+$ DOCKER_SANDBOXES_ENABLE_VIRTIOFS_CACHE=0 sbx run <agent>
 ```
 
 ## Networking

content/manuals/ai/sandboxes/get-started.md

@@ -47,7 +47,7 @@ Pick a project directory and launch an agent with
 
 ```console
 $ cd ~/my-project
-$ sbx run --name my-sandbox claude .
+$ sbx run --name my-sandbox claude
 ```
 
 The first time you run a sandbox, the CLI prompts you to choose a default
@@ -99,10 +99,10 @@ Each row shows a sandbox's name, the agent running in it, its status, any
 workspace — the host directory shared into the sandbox. That workspace is the
 one part of your machine the agent can see.
 
-Because you passed `.` as the workspace path, the current directory is shared
-read-write. The agent and your host see the same files. Edits the agent makes
-to your project appear in your working tree as it writes them, and you review
-them as an ordinary Git diff before committing.
+Because `sbx run` defaults the workspace to the current directory, your project
+is shared read-write. The agent and your host see the same files. Edits the
+agent makes to your project appear in your working tree as it writes them, and
+you review them as an ordinary Git diff before committing.
 
 Everything else runs inside the microVM, isolated from your host:
 

content/manuals/ai/sandboxes/troubleshooting.md

@@ -267,7 +267,7 @@ experience Git index corruption or unexpected file content, disable caching
 with the kill switch and recreate the sandbox:
 
 ```console
-$ DOCKER_SANDBOXES_ENABLE_VIRTIOFS_CACHE=0 sbx run <agent> .
+$ DOCKER_SANDBOXES_ENABLE_VIRTIOFS_CACHE=0 sbx run <agent>
 ```
 
 ## Clone mode reports "not in a Git repository" on WSL

content/manuals/ai/sandboxes/usage.md

@@ -27,7 +27,7 @@ The basic workflow is [`run`](/reference/cli/sbx/run/) to start,
 [`rm`](/reference/cli/sbx/rm/) to clean up:
 
 ```console
-$ sbx run claude .                  # start an agent in the current directory
+$ sbx run claude                    # start an agent in the current directory
 $ sbx ls                            # see what's running
 $ sbx stop my-sandbox               # pause it
 $ sbx rm my-sandbox                 # delete it entirely
@@ -45,7 +45,7 @@ If you need a clean slate, remove the sandbox and run it again:
 ```console
 $ sbx stop my-sandbox
 $ sbx rm my-sandbox
-$ sbx run claude .
+$ sbx run claude
 ```
 
 To remove all stopped local sandboxes, use `sbx prune`. Running sandboxes are
@@ -105,7 +105,7 @@ $ sbx run claude ~/my-project  # reconnects to same sandbox
 Use `--name` to give a sandbox an explicit identity:
 
 ```console
-$ sbx run claude --name my-project .
+$ sbx run --name my-project claude
 ```
 
 Once a named sandbox exists, use `--name` to re-attach to it from any working

content/manuals/ai/sandboxes/workflows/git.md

@@ -33,7 +33,7 @@ branches yourself.
 2. Start the sandbox. No special flags needed:
 
    ```console
-   $ sbx run claude .
+   $ sbx run claude
    ```
 
 3. The agent edits files in your working tree. Review diffs, stage, and