The mental model
Think of the inventory as one stock list for several stockrooms. Clawboo owns some of the stockrooms, so it can switch items on and off there. The others belong to a runtime: Clawboo can read the labels, and in one case ask the runtime to make a change, but it never rearranges a runtime’s own shelves.What the inventory shows
- Three kinds of entry: skills, tools and connectors.
- Where each one belongs: the runtime that owns it, and whether it belongs to one agent or to every agent on that runtime.
- A status: Ready, Disabled, Pending auth or Unavailable. An unavailable entry is greyed out, with the reason.
- The action Clawboo can take, if any: Enable or Disable. An entry Clawboo can only show reads “built-in, managed by” and the runtime’s name.
Where entries come from
The inventory reads from six sources. What Clawboo may do with an entry depends on its source.Connectors and grants
Connecting a connector makes it available, but gives it to no agent. An agent reaches a connector only through a grant: your permission for that agent to use it, with an access level and a rule for when to ask you first. You manage grants on the Org chart; Connectors has the steps. On the Org chart, each Boo’s tiles show its own entries plus the entries its runtime shares with every agent, such as built-ins. A connector tile appears on a Boo only when that agent holds a grant for it. A connector whose list of tools has changed since you approved it shows Changed since you approved it. Read what changed before you trust it again, rather than signing in again.What you control
- Switch entries on or off: in the Capabilities panel, for entries Clawboo owns and for OpenClaw’s allow and deny entries. See Capabilities.
- Add skills: install them from the Marketplace.
- Add connectors and decide who uses them: connect on the Connectors page, then give agents access on the Org chart. See Connectors.
- Approve tool calls: answer the approvals waiting at the top of the panel, or in Approvals.
Limits
- Clawboo never changes Hermes skills, or your own Claude Code settings in
~/.claude. - OpenClaw’s MCP servers and plugins cannot be switched from Clawboo; change them in OpenClaw.
- Codex entries cannot be changed from Clawboo.
- Clawboo cannot tell OpenClaw agents apart, so the connectors you give an OpenClaw agent on the Org chart do not reach it. Its use of apps through Composio asks for your approval each time.
Under the hood
Under the hood
- The record. Each entry is a
CapabilityRecord. Itsidhas the form<source>:<runtime>:<scope>:<agentId or global>:<kind>:<key>, and it carrieskind,scope(agentorglobalin practice),manageability,status,available,writable,hint,health(unknown,ok,needs-auth,degraded,errorordrift) and, for granted connectors,grantId. - Manageability.
managed: Clawboo owns it.external-write: the runtime owns the store and Clawboo would write through it (Codex, blocked today).runtime-of-record: the runtime owns it and Clawboo asks the runtime to change it (OpenClaw allow and deny lists).observe-only: read only. - Writes. The REST handler refuses an enable or disable on an
observe-onlyor non-writable entry with422, and an unknown entry with404. The panel hides more buttons than that: it offers none for unavailable or pending-auth entries either. An install takes the owning runtime from the agent’s own record, never from the request. - Degraded sources. Each source’s last good read is kept in the
capabilitiestable. When a source fails to read, its cached rows are served instead, and fresh rows win when both exist.
Related
- Capabilities: the Capabilities panel, step by step.
- Connectors: connect apps and servers, and give agents access.
- Org chart: every team’s Boos and their capability tiles.
- Teams, rooms and runtimes: what each runtime keeps to itself.
- Memory: the other shared resource every teammate uses.