docs: rename saas_runtime_mode to local_agent_server_mode

Update all references to match the rename in software-agent-sdk PR #2490:
- Rename parameter: saas_runtime_mode -> local_agent_server_mode
- Rename section heading: SaaS Runtime Mode -> Local Agent Server Mode
- Rename SVG files to match new naming
- Move automation_callback_url and automation_run_id to env vars table
- Update code examples to remove constructor args that are now env vars

Co-authored-by: openhands <openhands@all-hands.dev>

Author: openhands-agent

sdk/guides/agent-server/cloud-workspace.mdx

@@ -383,14 +383,14 @@ cd agent-sdk
 uv run python examples/02_remote_agent_server/10_cloud_workspace_share_credentials.py
 ```
 
-## SaaS Runtime Mode
+## Local Agent Server Mode
 
-Use `saas_runtime_mode=True` when your SDK script is **already running inside** an OpenHands Cloud sandbox — for example, as part of an automation workflow deployed to the cloud.
+Use `local_agent_server_mode=True` when your SDK script is **already running inside** an OpenHands Cloud sandbox — for example, as part of an automation workflow deployed to the cloud.
 
 ### When to Use This Mode
 
-| Scenario | Normal Mode | SaaS Runtime Mode |
-|----------|-------------|-------------------|
+| Scenario | Normal Mode | Local Agent Server Mode |
+|----------|-------------|-------------------------|
 | Script runs on your local machine | ✅ | ❌ |
 | Script runs in CI (GitHub Actions runner) | ✅ | ❌ |
 | Script deployed to run inside Cloud sandbox | ❌ | ✅ |
@@ -404,25 +404,23 @@ In **normal mode**, `OpenHandsCloudWorkspace` provisions a new sandbox via the C
   <img src="/sdk/guides/agent-server/images/normal-mode.svg" alt="Normal mode: Your machine communicates with OpenHands Cloud via API" />
 </Frame>
 
-In **SaaS runtime mode**, your script is already inside the sandbox and connects to the local agent-server:
+In **local agent server mode**, your script is already inside the sandbox and connects to the local agent-server:
 
 <Frame>
-  <img src="/sdk/guides/agent-server/images/saas-runtime-mode-simple.svg" alt="SaaS runtime mode: Script runs inside Cloud sandbox" />
+  <img src="/sdk/guides/agent-server/images/local-agent-server-mode-simple.svg" alt="Local agent server mode: Script runs inside Cloud sandbox" />
 </Frame>
 
 Key differences:
 - **No sandbox provisioning** — skips create/wait/delete lifecycle
 - **Connects to localhost** — talks to the agent-server already running in the sandbox
-- **SaaS credentials still work** — `get_llm()` and `get_secrets()` call the Cloud API
+- **Cloud credentials still work** — `get_llm()` and `get_secrets()` call the Cloud API
 
 ### Configuration
 
 | Parameter | Type | Default | Description |
 |-----------|------|---------|-------------|
-| `saas_runtime_mode` | `bool` | `False` | Skip sandbox provisioning, connect to localhost |
+| `local_agent_server_mode` | `bool` | `False` | Skip sandbox provisioning, connect to localhost |
 | `agent_server_port` | `int` | `60000` | Port of the local agent-server |
-| `automation_callback_url` | `str \| None` | `None` | URL to POST completion status on exit |
-| `automation_run_id` | `str \| None` | `None` | ID included in callback payload |
 
 ### Environment Variables
 
@@ -433,6 +431,8 @@ When running inside a Cloud sandbox, these environment variables are set automat
 | `SANDBOX_ID` | Sandbox identifier for `get_llm()` / `get_secrets()` |
 | `SESSION_API_KEY` | Session auth key (fallback: `OH_SESSION_API_KEYS_0`) |
 | `AGENT_SERVER_PORT` | Port override (optional) |
+| `AUTOMATION_CALLBACK_URL` | URL to POST completion status on exit (optional) |
+| `AUTOMATION_RUN_ID` | ID included in callback payload (optional) |
 
 ### Example: Automation Script Inside a Cloud Sandbox
 
@@ -446,15 +446,13 @@ from openhands.sdk import Conversation
 from openhands.tools.preset.default import get_default_agent
 
 with OpenHandsCloudWorkspace(
-    saas_runtime_mode=True,
+    local_agent_server_mode=True,
     cloud_api_url="https://app.all-hands.dev",
     cloud_api_key=os.environ["OPENHANDS_API_KEY"],
-    automation_callback_url=os.environ.get("CALLBACK_URL"),
-    automation_run_id=os.environ.get("RUN_ID"),
 ) as workspace:
     # No sandbox created — connects to local agent-server at localhost:60000
 
-    # SaaS credentials still work
+    # Cloud credentials still work
     llm = workspace.get_llm()
     secrets = workspace.get_secrets()
 
@@ -468,12 +466,12 @@ with OpenHandsCloudWorkspace(
     conversation.run()
     conversation.close()
 
-# On exit: completion callback sent automatically (if callback URL configured)
+# On exit: completion callback sent automatically (if AUTOMATION_CALLBACK_URL is set)
 ```
 
 ### Orchestration Pattern
 
-To deploy an automation script that uses SaaS runtime mode:
+To deploy an automation script that uses local agent server mode:
 
 1. **Create a sandbox** using normal mode (from your local machine or CI):
    ```python
@@ -490,14 +488,14 @@ To deploy an automation script that uses SaaS runtime mode:
    workspace.execute_command("python /workspace/my_automation.py")
    ```
 
-3. The script uses `saas_runtime_mode=True` to connect to the local agent-server
+3. The script uses `local_agent_server_mode=True` to connect to the local agent-server
 
 4. **Receive callback** when the script completes (optional)
 
 This pattern enables fire-and-forget automation where your orchestrator doesn't need to maintain a connection for the entire agent session.
 
 <Note>
-SaaS runtime mode is primarily used by the OpenHands automation service. For most SDK users, normal mode with `get_llm()` and `get_secrets()` provides a simpler experience.
+Local agent server mode is primarily used by the OpenHands automation service. For most SDK users, normal mode with `get_llm()` and `get_secrets()` provides a simpler experience.
 </Note>
 
 ## Next Steps

…rver/images/saas-runtime-mode-simple.svg …mages/local-agent-server-mode-simple.svgsdk/guides/agent-server/images/saas-runtime-mode-simple.svg renamed to sdk/guides/agent-server/images/local-agent-server-mode-simple.svg sdk/guides/agent-server/images/saas-runtime-mode-simple.svg renamed to sdk/guides/agent-server/images/local-agent-server-mode-simple.svg

@@ -112,10 +112,10 @@ For advanced orchestration, you may want to run SDK scripts *inside* a Cloud san
 - You need **nested agent execution** — an outer agent spawns inner agents
 - You're building an **automation service** that deploys user-provided scripts
 
-This uses `saas_runtime_mode=True`. See [SaaS Runtime Mode](/sdk/guides/agent-server/cloud-workspace#saas-runtime-mode) for the full pattern.
+This uses `local_agent_server_mode=True`. See [Local Agent Server Mode](/sdk/guides/agent-server/cloud-workspace#local-agent-server-mode) for the full pattern.
 
 <Frame>
-  <img src="/sdk/guides/agent-server/images/saas-runtime-mode.svg" alt="SaaS Runtime Mode orchestration pattern" />
+  <img src="/sdk/guides/agent-server/images/local-agent-server-mode.svg" alt="Local Agent Server Mode orchestration pattern" />
 </Frame>
 
 ### Enterprise: Self-Managed Infrastructure