Agent-Infrastructure on emsenn.net

Companion Tools for OpenClaw, March 2026

Mon, 09 Mar 2026 00:00:00 +0000

¶Purpose

This text surveys the tools that most often recur around OpenClaw in current official documentation and practical guide material as of March 9, 2026. The source base does not support exact usage counts, so “often used” here means recurring companions in the current OpenClaw ecosystem rather than measured market share.

¶What the tool stack reveals

The current OpenClaw ecosystem is converging on a distinctive practice. OpenClaw itself stays as the long-running control plane, memory layer, and multi-channel agent surface. Specialized work is pushed outward:

OpenClaw Gateway

Mon, 09 Mar 2026 00:00:00 +0000

The OpenClaw Gateway is the long-running control-plane process in an OpenClaw deployment. It coordinates sessions, channels, tools, configuration, routing, and web interfaces while the assistant remains the user-facing product surface.

¶Role

The Gateway gives OpenClaw a persistent runtime. It keeps the assistant reachable through chat channels, the Control UI, WebChat, and paired device surfaces without reducing the system to a single interactive terminal session.

¶Trust boundary

OpenClaw’s security model treats the Gateway as a trusted operator boundary, not as a hostile multi-tenant service. Within one Gateway instance, authenticated control-plane access carries authority over the configured agents, sessions, and policies in that deployment.

OpenClaw Hook

Mon, 09 Mar 2026 00:00:00 +0000

An OpenClaw hook is a directory-discovered event handler that runs when command or lifecycle events fire inside the Gateway. Hooks are the event-driven automation layer of OpenClaw.

¶Structure

The official hooks docs describe a hook as a directory containing HOOK.md plus a TypeScript handler. Hooks are discovered from workspace, managed, and bundled directories, with workspace hooks having highest precedence.

¶Role

Hooks let operators attach automation to events such as /new, bootstrap, or gateway startup. The bundled session-memory, bootstrap-extra-files, command-logger, and boot-md hooks show the main current uses: memory capture, workspace augmentation, audit logging, and startup actions.

OpenClaw Memory

Mon, 09 Mar 2026 00:00:00 +0000

OpenClaw memory is the Markdown-based memory layer in an OpenClaw workspace. Its source of truth is written files on disk rather than session-local model state.

¶Structure

The official memory docs describe two default durable layers:

MEMORY.md for curated long-term memory
memory/YYYY-MM-DD.md for dated logs and running context

Memory search tools are provided by the active memory plugin, but the files remain primary. Search augments retrieval; it does not replace the underlying Markdown record.

OpenClaw Node

Mon, 09 Mar 2026 00:00:00 +0000

An OpenClaw node is a paired device surface that exposes host-local capabilities to an OpenClaw Gateway. Nodes let the assistant act through device-specific interfaces such as voice, camera, screen capture, notifications, and host-local command execution.

¶Pairing model

OpenClaw documents node pairing as an operator-approved connection to a Gateway. Once paired, node actions are treated as trusted operator actions on that device rather than as requests from an untrusted external sender.

OpenClaw Plugin Slot

Mon, 09 Mar 2026 00:00:00 +0000

An OpenClaw plugin slot is an exclusive plugin category where only one plugin can own a given runtime role at a time. Slots let OpenClaw keep its core lean while making selected extension points explicit and mutually exclusive.

¶Examples

OpenClaw documents memory and contextEngine as plugin slots. If multiple plugins declare the same exclusive kind, only the selected plugin loads for that slot and the others remain disabled.

OpenClaw Skill

Mon, 09 Mar 2026 00:00:00 +0000

An OpenClaw skill is a directory-based instruction and tool bundle that teaches an OpenClaw agent how to perform a specialized task. The official docs define a skill as a directory containing a SKILL.md file and, optionally, scripts or other resources.

¶Loading model

The official skills documentation describes three main loading locations:

bundled skills shipped with OpenClaw
managed or local skills under ~/.openclaw/skills
workspace skills under <workspace>/skills

When names conflict, workspace skills take precedence over shared and bundled skills.

OpenClaw SOUL.md

Mon, 09 Mar 2026 00:00:00 +0000

OpenClaw SOUL.md is a workspace file that defines the assistant’s identity, style, values, and behavioral boundaries. In practice it is the main place where an operator specifies how the assistant should speak, what it should prioritize, and where it should stop.

¶Role

The official bootstrapping flow writes SOUL.md during first-run setup after collecting identity and preference information. Independent setup guides treat it as the highest-leverage file to write early because it shapes every later interaction.