ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-27 12:56:01 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs(agents): restore the non-default scope for systemAgent ownership (#126431)

Browse Source 
Live-testing #126377 in a real explicit fleet surfaced an inaccuracy that PR
introduced. It dropped 'Other agent-scoped methods do not use this setting as a
general default', which is still true: only models.list, models.authStatus,
skills.status, and doctor.memory.status opt in, while the generic Gateway
resolver in agent-id-shared.ts deliberately does not.

Verified against a live gateway and CLI on a three-agent explicit fleet with
systemAgent.agentId set: 'openclaw models list', 'openclaw sessions', stored
session lookup, and TUI startup all still require an explicit agent. Name those
surfaces so operators know where the owner does and does not apply.
This commit is contained in:
Peter Steinberger
2026-08-19 13:08:34 -07:00
committed by GitHub
parent 24a1139188
commit fd2fccbc8e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gateway/config-agents.md
+1 -1
View File
@@ -588,7 +588,7 @@ Selects the agent whose model and credentials own ambient OpenClaw system work:
}
```
An explicit request `agentId` always wins. Delegated consults with a requesting agent keep that requester as their owner. Surfaces that enumerate or narrow across agents deliberately do not adopt this owner, because silently picking one agent would hide the others: session-store selection (`openclaw sessions`) and `openclaw hooks` status still require `--agent <id>` (or `--all-agents`). When `systemAgent.agentId` is absent, a sole configured agent resolves implicitly; ambient work in a multi-agent fleet then fails with an actionable error, except queued-delivery recovery, which records the failing delivery and keeps draining the rest of the queue. Upgrade-only ownership lives at `agents.defaults.authInheritance.agentId` for inherited credentials and `agents.defaults.sessionStore.agentId` for retired `main` session rows or unscoped rows in a fixed `session.store`.
An explicit request `agentId` always wins. Delegated consults with a requesting agent keep that requester as their owner. The four reads above opt in individually; other agent-scoped Gateway methods, such as `tools.*`, `commands.*`, chat history, and session-catalog reads, do not use this setting as a general default. Surfaces that pick one agent's view also keep requiring an explicit choice, because silently adopting this owner would hide the other agents: `openclaw sessions` (add `--agent <id>` or `--all-agents`), `openclaw hooks` status, `openclaw models`, stored session lookup by id, and TUI startup. When `systemAgent.agentId` is absent, a sole configured agent resolves implicitly; ambient work in a multi-agent fleet then fails with an actionable error, except queued-delivery recovery, which records the failing delivery and keeps draining the rest of the queue. Upgrade-only ownership lives at `agents.defaults.authInheritance.agentId` for inherited credentials and `agents.defaults.sessionStore.agentId` for retired `main` session rows or unscoped rows in a fixed `session.store`.
### `agents.defaults.compaction`