OpenClaw notifier
Deliver notifications through a local OpenClaw gateway — personal, low-latency, private.
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 openclawIt will:
- Auto-detect OpenClaw on
localhost(or prompt for the URL). - Exchange / generate an auth token.
- Write
agent-orchestrator.yaml,~/.openclaw/openclaw.json, and a shell-profile export forOPENCLAW_HOOKS_TOKEN.
Non-interactive variant:
ao setup openclaw --non-interactive --url http://127.0.0.1:18789/hooks/agent --token <token>Use
After setup, your config looks like:
notifier:
- type: openclaw
url: http://127.0.0.1:18789/hooks/agent
token: ${OPENCLAW_HOOKS_TOKEN}
wakeMode: next-heartbeat # or `now`Config
| Key | Default | What it does |
|---|---|---|
url | http://127.0.0.1:18789/hooks/agent | OpenClaw hook endpoint |
token | — | Auth token. Use ${ENV_VAR} — never commit the raw value |
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 |
configPath | ~/.openclaw/openclaw.json | Override OpenClaw config location |
Token precedence
Token is read in this order:
tokeninagent-orchestrator.yaml(usually${OPENCLAW_HOOKS_TOKEN})- Env var
OPENCLAW_HOOKS_TOKEN ~/.openclaw/openclaw.json
ao doctor --test-notify is the only notifier test that can probe OpenClaw without side effects — other notifiers send a real test message.