blueclawCapabilities
A capability is an operation a separate service performs on the agent's behalf, such as sending a message, changing a calendar, or running a model.
blueclaw stays provider-neutral. It asks for a capability and passes an executionMode (device, companion, remote or auto, default auto); the capability service decides where it runs. The one choice blueclaw makes itself is sending companion for a tool whose privacyClass is user_browser. Descriptors mark tools that need the requester present (requiresUserPresence), their own device (requiresRequesterDevice) or a companion browser; tools that need the user present are not registered for scheduled runs.
The capabilities block names the service: endpoint, unixSocketPath, or vsockCID and vsockPort for a guest, plus timeoutSecond. The request and response shapes are Zod contracts in protocol/ (capability-descriptor, capability-registry-response, tool-invoke-request, tool-invoke-response). A deployment without the block reports capabilityd: not_configured in health and runs without capability tools, capability-routed models, or memory embeddings.