DEV Community: Verdeoc

A concrete OpenClaw workflow: notify your iPhone when an agent finishes

Verdeoc — Sun, 18 Oct 2026 19:41:40 +0000

A concrete OpenClaw workflow: notify your iPhone when an agent finishes

A long-running OpenClaw task can finish after you leave the Gateway chat. This tutorial shows one narrow workflow: deliver a native iOS notification for the supported agentFinished event using reply-push-v2.

This is a notification path for a plugin-owned event. It is not a fix for OpenClaw core Web Push, the Control UI, the Gateway, or the browser relay.

What you need

OpenClaw Gateway running on a machine you control
The official OpenClaw iOS app with a paired iPhone node
The reply-push-v2 plugin, version 2.1.1 at the time of writing
A task that reaches the supported agentFinished event

The package was checked from a clean npm package install/load test. That verifies package structure and loading; it does not prove delivery on every iOS, network, or Gateway configuration.

Install

Install the plugin from npm:

openclaw plugins install reply-push-v2

The repository also documents a manual fallback if the normal npm installation path is unavailable:

Do not paste Gateway or APNs credentials into a prompt. Use the configuration path documented by the project and review third-party plugin permissions before enabling it.

The workflow

Pair the official iOS node with the Gateway.
Install and enable reply-push-v2.
Start a task that may run longer than your current chat session.
Leave the desktop or chat surface.
When the task reaches agentFinished, check the paired iPhone for the native notification.

A practical prompt can be simple:

Run the requested task and notify my paired iPhone only when it finishes. Do not send intermediate updates.

For scheduled work, the same pattern applies: the scheduler starts the task, and the completion event is the notification trigger. No test post, payment, or external webhook is needed for this workflow.

Verification checklist

Use this sequence when diagnosing a missing notification:

Confirm the iPhone node is paired and reachable from the Gateway.
Confirm the plugin is installed and enabled with openclaw plugins list.
Run a small task that reliably completes.
Check whether the task itself finished before diagnosing delivery.
Check the iOS app notification permission and Focus settings.
Inspect the Gateway/plugin logs without copying tokens or private payloads.

If the task finishes but the notification path does not, collect the event timing and node reachability first. Do not describe that symptom as a core OpenClaw Web Push or relay fix: this plugin does not claim to repair those systems.

Free boundary and limitations

The Free edition covers the documented agentFinished category. Other event categories are part of the project's separately documented Pro offering. This tutorial does not promise delivery guarantees, background execution on every iOS state, or compatibility with an unpaired device.

The workflow also depends on the official app/node, the Gateway being able to reach it, and the user's iOS notification permissions. A browser tab, PWA, or X/Reddit/Discord integration is not required.

Native iOS push notifications for your OpenClaw agents (no PWA)

Verdeoc — Sat, 03 Oct 2026 19:02:43 +0000

OpenClaw agents run on a Mac (a Gateway). You talk to them from Telegram, the Control UI, or the official iOS app. Once you close the app, you can miss agent events unless you keep a PWA open.

I built reply-push-v2, an OpenClaw plugin that sends native APNs push notifications to the official OpenClaw iOS app. No PWA, no background tab, no polling.

Free edition 2.1.1: agentFinished notifications.
Pro edition: agentQuestion, humanMentioned, scheduledTaskFailed, and subagentFailed, plus an optional agent allowlist and custom mention regex.

Compatibility

Package: 2.1.1
OpenClaw build target: 2026.9.6
Plugin API: >=2026.3.24-beta.2

Why native

Your Gateway holds no APNs keys: notifications go through the hosted OpenClaw push relay (ios-push-relay.openclaw.ai). The plugin auto-detects your paired iPhone node, so a single-device setup needs zero device configuration. It respects NIGHT_MODE and dedupes per category for 15 seconds.

Requirements

OpenClaw Gateway with plugin support
Official OpenClaw iOS app, paired and approved with the Gateway
iOS notifications enabled for the app
Reachability to ios-push-relay.openclaw.ai
iOS only; Android is not supported

Install (recommended)

Install the free package with npm:

openclaw plugins install reply-push-v2

Enable the plugin and its conversation hook in ~/.openclaw/openclaw.json:

{
  "plugins": {
    "entries": {
      "reply-push-v2": {
        "enabled": true,
        "hooks": { "allowConversationAccess": true }
      }
    }
  }
}

Restart the Gateway and verify:

openclaw plugins list

You should see the Free edition with agentFinished enabled. Ask your agent to complete a turn and check the iPhone lock screen.

Manual fallback

If npm installation is unavailable, unzip the package into ~/.openclaw/plugins/reply-push-v2/, add the same plugins.entries entry above, restart the Gateway, and run openclaw plugins list.

DEV Community: Verdeoc

A concrete OpenClaw workflow: notify your iPhone when an agent finishes

A concrete OpenClaw workflow: notify your iPhone when an agent finishes

What you need

Install

The workflow

Verification checklist

Free boundary and limitations

Links

Native iOS push notifications for your OpenClaw agents (no PWA)

Compatibility

Why native

Requirements

Install (recommended)

Manual fallback

Links