openclaw-support-kb

Use for Paperclip, Mission Control, companies, goals, org charts, agents, tickets, heartbeats, budgets, approvals, dashboard, API, CLI, deploy, adapter, or board-operator questions.

Use when a customer question may involve OpenClaw, Hermes Agent, Paperclip Mission Control, Composio integrations, cross-agent repair, system setup, config, messaging, or support and the target system must be identified before answering.

Use for evaOS Live Browser, KasmVNC, VNC, visible Chromium, CDP, screenshots, authenticated browser handoff, Arbostar UI, WPForms production lead tests, or browser-based customer tool operation.

Use when OpenClaw, Hermes Agent, or Paperclip must diagnose or repair another system, when the acting agent and broken target are different, or when docs from multiple systems might conflict.

Use for Hermes Agent setup, gateway, Telegram/messaging, config.yaml, skills, memory, sessions, MCP, cron, provider, update, or troubleshooting questions. Search the local Hermes namespace before using OpenClaw or Paperclip docs.

Use when a user or agent needs to inspect, change, repair, validate, or troubleshoot OpenClaw config, openclaw.json, channel config, SecretRefs, plugins.entries config, or startup failures caused by invalid config.

Use when the user wants to find, evaluate, install, update, or improve OpenClaw skills or small-business integrations. Search the local VoltAgent skills snapshot, ClawHub/OpenClaw skill search, and Composio integration path; pin candidate sources and run Snyk agent-scan before skill install.

Use for OpenClaw setup, channel configuration, update, runtime, troubleshooting, and support questions. Search the local GBrain OpenClaw support KB first and answer with citations instead of guessing.

Use when OpenClaw support should be contacted, including escalation to @evaOS_support_bot or support@electricsheephq.com. Draft and redact first; ask the user before sending. Prefer GOG for email when available.