OpenClawMachines

Use OCM workspace integrations exposed by the native `mcp.servers.ocm` MCP server. Trigger when a user asks to use connected workspace apps or external SaaS tools such as Google Workspace, GitHub, Jira, Linear, Slack, Notion, custom REST APIs, OpenAPI tools, or remote MCP servers through OCM.

Debug OpenClaw Machines profile, auth, Worker routing, host enrollment, agent API, Firecracker, rootfs, and VM runtime behavior by choosing the right boundary and proof before changing code.

Review OpenClaw Machines changes by tracing behavior beyond the diff, checking ownership boundaries, and requiring focused proof for bug fixes.

Plan, implement, or review local/operator/self-hosted OpenClaw Machines work without leaking secrets or smuggling hosted-only assumptions into public core.

Choose and run the smallest safe OpenClaw Machines verification path for backend, frontend, Worker, host enrollment, Firecracker, rootfs, and self-hosted changes.

Drive a browser from an OpenClaw machine. Companion to the browser-harness skill — explains the OCM-specific bridge proxy, the readiness check you must run first, and how pairing works. Start here before writing any browser code.