Slot: notifier · Name: openclaw

macOSSupported

LinuxSupported

WindowsSupported

OpenClaw is a local gateway that routes AO events into whatever personal alert channel you've wired up — phone push, email, a local sound, etc. If it's running on your machine, this notifier uses it.

Setup

Run AO's interactive helper:

ao setup openclaw

It will:

Auto-detect OpenClaw on localhost (or prompt for the URL).
Read hooks.token from your OpenClaw config.
If the token is missing, show where to add/generate it from the OpenClaw side.
Write only agent-orchestrator.yaml; AO does not generate the token or write shell-profile exports.
Let you review and change the URL, OpenClaw config path, or routing preset before saving.

Non-interactive variant:

ao setup openclaw --non-interactive --url http://127.0.0.1:18789/hooks/agent --routing-preset urgent-action

Refresh an existing setup or inspect status:

ao setup openclaw --refresh
ao setup openclaw --status

Use

After setup, your config looks like:

notifiers:
  openclaw:
    plugin: openclaw
    url: http://127.0.0.1:18789/hooks/agent
    openclawConfigPath: ~/.openclaw/openclaw.json
    wakeMode: now

The OpenClaw config keeps the actual secret:

{
	"hooks": {
		"enabled": true,
		"token": "<openclaw-hooks-token>",
		"allowRequestSessionKey": true,
		"allowedSessionKeyPrefixes": ["hook:"]
	}
}

Config

Key	Default	What it does
`url`	`http://127.0.0.1:18789/hooks/agent`	OpenClaw hook endpoint
`openclawConfigPath`	`~/.openclaw/openclaw.json`	Local OpenClaw config path that contains `hooks.token`
`token`	—	Remote/manual fallback. Avoid for local setups because it stores the secret in AO config
`name`	—	Identifier shown in OpenClaw
`sessionKeyPrefix`	—	Prefix for OpenClaw session keys
`wakeMode`	`next-heartbeat`	`now` = deliver immediately, `next-heartbeat` = batch on next OpenClaw tick
`deliver`	`true`	Disable to record-only without waking the user
`retries`	`3`	Retry count on transient failures
`retryDelayMs`	`1000`	Base retry delay
`healthSummaryPath`	—	Optional local path where OpenClaw writes a summary AO can pick up

Token precedence

Token is read in this order:

token in agent-orchestrator.yaml if explicitly configured
hooks.token from openclawConfigPath
Env var OPENCLAW_HOOKS_TOKEN as a legacy fallback

ao setup openclaw --status probes the OpenClaw gateway and token. To send a real AO test notification through the configured notifier, run:

ao notify test --to openclaw --template basic