Skip to content

Add experimental WhatsApp Personal connector (Baileys bridge)#315

Open
rohitprasad15 wants to merge 1 commit into
mainfrom
feat/coworker-whatsapp-personal
Open

Add experimental WhatsApp Personal connector (Baileys bridge)#315
rohitprasad15 wants to merge 1 commit into
mainfrom
feat/coworker-whatsapp-personal

Conversation

@rohitprasad15

@rohitprasad15 rohitprasad15 commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

The first connector behind the experimental gate (#314): two-way WhatsApp on a personal account using Baileys (the unofficial WhatsApp Web protocol library) in a supervised Node.js sidecar.

  • Sidecar (experimental/whatsapp_bridge/): streams inbound messages, pairing QRs, and connection state as NDJSON events on stdout — no inbound HTTP, no polling. The only listener is a loopback POST /send for the stateless send_message tool. QR pairing, self-chat mode default, one npm dependency installed into the state dir on first connect (never vendored, never in release artifacts).
  • Adapter + registration hooks: small registries in config/adapters/senders let the experimental package add platforms to the existing gateway; the gateway skips experimental platforms unless the opt-in setting is on. New GET /v1/connectors/{name}/status surfaces pairing state and the QR from the cached event stream.
  • Risk gating: blunt account-ban risk_notice required at connect; excluded from release builds like all experimental code.

9 new offline tests (registration, gating, settings, event mapper, event-stream handling, sender routing, credential-less send_message, gateway opt-in skip). Full suite: 308 passed, 1 skipped; bridge.js syntax-checked.

Two-way WhatsApp on a personal account via a supervised Node.js sidecar
built on Baileys (unofficial WhatsApp Web protocol). The sidecar streams
inbound messages, pairing QRs, and connection state as NDJSON events on
stdout — no inbound HTTP, no polling; its only listener is a loopback
POST /send for the stateless send_message tool. Registration hooks
(platforms, adapter factories, sender credentials) plug the experimental
package into the existing gateway, which skips experimental platforms
unless the opt-in setting is on. QR pairing via a new
/v1/connectors/{name}/status endpoint; npm deps install into the state
dir on first connect (never vendored); blunt account-ban risk notice
gates connect; excluded from release builds like all experimental code.
@rohitprasad15 rohitprasad15 force-pushed the feat/coworker-whatsapp-personal branch from cad63ba to bdfdd52 Compare June 12, 2026 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant