OpenClaw

Context

The gateway coordinates sessions, channel messages, workspace context, memory, skills or plugins, connected nodes, and tool results.

Actions

Routes messages to agents that can use configured tools, execute commands, work with files and services, and respond through connected channels.

Execution

Runs as a self-hosted Gateway process on the operator's machine or server; chosen models may run locally or through external providers.

Memory & rules

Workspace files, sessions, memory, and installed extensions provide persistent state. Exact behavior depends on the configured agent and plugins.

Permissions

The operator controls hosting, channels, provider credentials, tools, and plugins. Self-hosting increases control but does not make plugins, messages, or model calls automatically private or safe.

Verification

Gateway logs, session history, explicit approvals, and isolated execution can support review. Reliable verification depends on which tools and policies the operator configures.

Best for

• A personal assistant reachable from several chat apps
• Self-hosted routing and model choice
• Developers comfortable maintaining an always-on gateway

Limitations

• Editorial judgment: users who do not want to secure and maintain a public-facing service
• Editorial judgment: sensitive automation before channel, plugin, and credential boundaries are audited