fix: scope process sessions per agent

docs/gateway/background-process.md

@@ -51,6 +51,7 @@ Notes:
 - Only backgrounded sessions are listed/persisted in memory.
 - Sessions are lost on process restart (no disk persistence).
 - Session logs are only saved to chat history if you run `process poll/log` and the tool result is recorded.
+- `process` is scoped per agent; it only sees sessions started by that agent.
 - `process list` includes a derived `name` (command verb + target) for quick scans.
 - `process log` uses line-based `offset`/`limit` (omit `offset` to grab the last N lines).
 

docs/tools/bash.md

@@ -9,6 +9,7 @@ read_when:
 
 Run shell commands in the workspace. Supports foreground + background execution via `process`.
 If `process` is disallowed, `bash` runs synchronously and ignores `yieldMs`/`background`.
+Background sessions are scoped per agent; `process` only sees sessions from the same agent.
 
 ## Parameters
 

docs/tools/index.md

@@ -53,6 +53,7 @@ Core actions:
 Notes:
 - `poll` returns new output and exit status when complete.
 - `log` supports line-based `offset`/`limit` (omit `offset` to grab the last N lines).
+- `process` is scoped per agent; sessions from other agents are not visible.
 
 ### `browser`
 Control the dedicated clawd browser.