v0.1.0 - notification channels + guided setup

Self-hosted WhatsApp bridge for AI agents: one paired number exposed via REST, MCP, and a web UI, built on Baileys with a single SQLite file for storage.

Highlights

• REST API (127.0.0.1:8080/v1) - conversations, messages, send, aliases, webhook test
• MCP server (stdio) - ~20 tools for Claude Code, Codex, or any MCP-capable agent, with a safety contract in AGENTS.md
• Web UI - single-page inbox with bearer-token login
• Inbound webhook - every received message POSTed to a URL of your choice, with retries
• Full history backfill on first pair, LID/phone alias merging, display-name resolution
• Autoreply sidecar (optional) - drafts replies in your own voice via Claude, delivers them for review, and can auto-send under strict safety gates (confidence threshold, sensitive-topic blocks, cooldowns, group protection)

New in this release

• Selectable notification channels: draft notifications can now go to Telegram, Slack, your own WhatsApp number (self-chat or a second number, sent through the bridge itself), or a generic webhook - pick one with AUTOREPLY_NOTIFY_CHANNEL
• Guided setup wizard: npm run autoreply:setup-notify walks you through credentials per channel, writes .env, and sends a test notification
• Loop protection: the WhatsApp notify chat is excluded from autoreply processing, so notifications can never generate drafts about themselves
• SOPs: step-by-step setup guides for humans (docs/sop-notifications-human.md) and AI agents (docs/sop-notifications-agent.md)
• Expanded README: full explanation of the autoreply pipeline, how the confidence threshold and safety gates work, and the notification channels
• Cross-platform guide: docs/cross-platform.md documents the exact patch list for Linux and Windows (WSL2 recommended)

Install

git clone https://github.com/obirimensah05/whatsapp-bridge.git
cd whatsapp-bridge
npm install
npm run pair -- main <countrycode+digits>

Requires Node 20+. See the README for pairing, service setup, and the full API table.