Push Notifications

Why push?

ManyWe relays are content-blind, but you still want to know when a friend messages you. Push notifications deliver new-message previews to your IM chat (Telegram, Discord, WhatsApp, ~21 channels) within seconds, without the relay seeing the content.

Architecture

ManyWe Push data flow: Alice's daemon → ManyWe Relay → Bob's daemon → SSE → hook.py service → IM Bot → Bob's IM chat

3-step setup

Step 1 — Install ManyWe

Follow the Getting Started guide. ManyWe runs as a local daemon on macOS, Linux, or Windows.

Step 2 — Run `manywe_push_register_auto` in your AI chat

In the AI chat where ManyWe is registered as an MCP server (OpenClaw, Claude Desktop, Cursor, Hermes), say:

register a ManyWe push route

Your AI calls manywe_push_register_auto. ManyWe prints a one-time proof code that looks like MW-PUSH-A3F2C9.

Step 3 — Paste the proof code into your IM chat

Open the IM chat where you want to receive notifications (e.g. a Telegram chat with your host's bot, a Discord DM with the OpenClaw bot, or a WhatsApp thread with Hermes-Neonize). Paste the proof code there.

The host agent's send-primitive completes the round-trip with ManyWe, the route registers, and ManyWe replies in your AI chat with Push registered ✓.

Supported IM channels

Push notifications are delivered through 21+ IM channels via your host agent's send-primitive (OpenClaw openclaw message send covers ~21 channels including Telegram, Discord, WhatsApp, Feishu, WeChat, Slack, Mattermost, Element, Signal-CLI bridge, Matrix, IRC, XMPP, Line, KakaoTalk, Viber, Threema, Wire, RocketChat, Zulip, Microsoft Teams, and Google Chat; Hermes send_message_tool covers Telegram, Discord, and WhatsApp via Neonize).

The exact channel set depends on which host agent you use and which platform credentials it has configured. Run manywe_status to see which channels your installed host advertises.

Privacy boundary

ManyWe Relay never sees push content (P0 hard rule). Push notifications are delivered by your host agent's existing send-primitive (OpenClaw 21 channels, Hermes), not by ManyWe directly. ManyWe doesn't call IM platform APIs. (See P11 in CLAUDE.md.)

What this means in practice:

The ManyWe relay routes opaque encrypted blobs and emits a notification metadata event when a new envelope arrives.
The notification metadata (sender display name, timestamp, unread count) is delivered to your local manywe-agentd via SSE.
Your local hook.py service forwards the metadata to your host agent's existing IM send-primitive.
The host agent — not ManyWe — calls the actual IM platform API (Telegram Bot API, Discord webhook, WhatsApp Cloud API, etc.).

This boundary keeps ManyWe out of the IM-platform integration business and limits the blast radius of any platform-side compromise.

What happens if push isn't working?

See the push diagnostic checklist in our troubleshooting guide. Typical causes: the daemon isn't running, the proof code was pasted in the wrong chat, the IM bot is offline, or your host agent hasn't been granted send permission in the target chat.

Copy-paste phrases

If you're not sure what to say to your AI agent, paste any of these into your AI chat. ManyWe's intent matcher recognises them all:

configure push
set up push
set up push notifications
configure ManyWe push
enable push
configure ManyWe push for this chat

The agent will respond with a MW-PUSH-XXXXXX proof code. Paste that proof code into the IM chat where you want notifications to land — ManyWe finishes the registration automatically.