You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/install/quickstart.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,6 +180,11 @@ Common flags:
180
180
-`--with-airlock` / `-WithAirlock` turns on airlock-mediated outbound downloads in the sandbox runtime policy.
181
181
-`--with-inference` / `-WithInference` and `--with-diffusion` / `-WithDiffusion` enable the heavier model-serving profiles.
182
182
183
+
The sandbox launcher now starts a loopback-only, token-authenticated host
184
+
controller so the UI can apply these same profile changes from Settings and
185
+
service-specific buttons without mounting the Docker socket into the UI
186
+
container.
187
+
183
188
> **Security note:** This is a lower-assurance path than the full OS or VM image. The host kernel and container runtime can inspect container memory, mounted files, and network activity. Use it for evaluation and workflow testing, not sensitive workloads.
Copy file name to clipboardExpand all lines: docs/install/sandbox.md
+17-2Lines changed: 17 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,8 +57,10 @@ The helper script will:
57
57
58
58
1. Create `deploy/sandbox/.env` from the template if needed.
59
59
2. Generate a per-stack service token in `deploy/sandbox/runtime/service-token`.
60
-
3. Render a runtime policy/config overlay for the selected profiles.
61
-
4. Build, harden, and wait for the sandbox services to become healthy.
60
+
3. Generate a separate host-control token in `deploy/sandbox/runtime/control-token`.
61
+
4. Start a loopback-only host controller used by the UI for profile/service automation.
62
+
5. Render a runtime policy/config overlay for the selected profiles.
63
+
6. Build, harden, and wait for the sandbox services to become healthy.
62
64
63
65
Then open:
64
66
@@ -70,6 +72,13 @@ http://127.0.0.1:8480
70
72
71
73
The default stack starts the control plane only. Inference and diffusion are opt-in because they are heavier and usually need user-supplied model paths or extra runtime dependencies.
72
74
75
+
When the stack is started through `secai-sandbox.cmd` or `scripts/sandbox/start.*`,
76
+
the UI can start these profiles for you from **Settings**, **Chat**, **Models**, or
77
+
**Generate**. The UI does not receive the Docker socket; it calls a host-side
78
+
controller on `127.0.0.1:${SECAI_CONTROL_PORT:-8498}` with a random bearer token
79
+
mounted read-only into the UI container. The controller only accepts allowlisted
0 commit comments