docs(openclaw): stop advising a per-spawn env for spawned sessions

OpenClaw's sessions_spawn has no env argument (openclaw/openclaw#51654
was closed without adding one), so the documented
env: { OPENCLAW_SESSION: "1" } silently did nothing. Point users at the
ACP harness or Gateway environment instead and guard the old advice.
Adopts #2749.

Co-authored-by: DanCanadian <211164803+DanCanadian@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
committed 2026-10-08 06:15:45 +00:00
1 parent ebb5d39b8e
commit dfeae47a17
2 files changed
+12 -1

No files matched your search

+7 -1
View File
@@ -127,7 +127,13 @@ environment variable should be set. gstack detects this and adjusts:
rendering prose to nobody
- Focuses on task completion and prose reporting
Set the env var in sessions_spawn: `env: { OPENCLAW_SESSION: "1" }`
`sessions_spawn` has no per-spawn environment argument
([openclaw/openclaw#51654](https://github.com/openclaw/openclaw/issues/51654)
was closed without adding one), so an `env` field in the tool call is ignored.
Set `OPENCLAW_SESSION=1` in the environment of the Claude ACP harness or the
Gateway service instead, keep credentials out of that wrapper, and confirm the
variable from inside the spawned process (for example `echo $OPENCLAW_SESSION`)
rather than trusting the session's final message.
### Explicit override: GSTACK_SESSION_KIND