Agent action surfaces

OpenClaw Tools

Map the action layer: built-in tools, custom tools, provider-backed tools, browser actions, exec policy, and direct Gateway tool invocation.

CoClaw is community-run and independent from the official OpenClaw project. Use official OpenClaw docs for canonical command, schema, and release details.

Official docs All CoClaw hubs

Register actions deliberately

Custom tools should have narrow names, clear parameters, and operator-visible failure modes.

Read next

Control exec paths

Shell and local process access should be constrained with approvals and safe-bin patterns before broader channel rollout.

Read next

Debug non-use

When the agent only chats, check model/tool compatibility, config scope, and provider responses before assuming user error.

Read next

CoClaw reading path

Community pages are intentionally narrower than upstream docs. Use them to choose a path, then return to official references for exact commands and schema fields.

Custom tools guide

CoClaw setup notes for extending the action surface.

Open

Tools after update

Community triage path for tool-call regressions.

Open

Config generator

Generate safer starter config without hand-editing every key.

Open

Other current OpenClaw surfaces

These CoClaw hubs are first-pass orientation pages, not exhaustive docs.

CoClaw treats OpenClaw v2026.6.1, published June 3, 2026, as the latest stable baseline for this first-pass map. Main branch and beta builds can move faster and should not be presented as stable.

Platforms Start here when the question is macOS app, Windows, Linux, VPS, Raspberry Pi, iOS, Android, or cloud hosting. Nodes Use this hub when a workflow depends on a paired device, node permissions, Canvas, media capture, or remote browser control. Plugins Use this hub when a capability lives outside the core Gateway or when an operator is evaluating ClawHub packages. Providers Use this hub when the hard problem is not the channel, but the model/provider path behind the agent. Automation Use this hub when OpenClaw is expected to initiate or continue work outside a single live chat reply.