Mediator

Mediator is a personal messaging assistant. You connect your messaging accounts — WhatsApp, Facebook Messenger, or a public on-site chat page — and, for each contact, an AI mediator with a system prompt of your choosing handles the conversation on your behalf.

How it fits together

You (OWN) — the account you log into Mediator with, using Google or Facebook OAuth.

Contacts (OTH) — the people who message you on the platforms you've connected. Each contact gets its own mediator config: a system prompt, an optional memory field, and tools the AI can call (calendar lookups, etc.).

The mediator loop — every time a message arrives from a contact, the app:

1. Loads the contact's mediator config and the last ~20 messages.
2. Sends them plus the system prompt to your chosen AI provider (Anthropic, OpenAI, Groq, xAI, OpenRouter, z.ai).
3. Dispatches whatever the AI decided: reply with text, mark a message with an emoji, wait for confirmation, call a tool, or update the memory.

The dispatch shows up in real time in your admin panel and on the platform the contact used.

Getting started

1. Log in at the login screen with Google or Facebook.
2. Set up an AI provider in Settings. You need an API key from at least one of Anthropic, OpenAI, Groq, xAI, OpenRouter, or z.ai. The app never charges you — you pay the provider directly.
3. Connect a messaging platform: WhatsApp, Facebook Messenger, or an on-site chat link.
4. Configure the mediator per contact: open a contact from the Contacts page, write a system prompt, enable it.

What each platform can do

Platform	Read messages	Send messages	Notes
WhatsApp	✅	✅	Uses your personal WhatsApp account via a QR-code pairing, like WhatsApp Web.
Facebook Messenger	⚠️ groups + non-E2EE	✅ groups + non-E2EE	Personal end-to-end-encrypted chats aren't accessible; see the Facebook docs page for details.
On-site chat	✅	✅	A public link you share; anyone with the link can start a conversation.

Why this exists

The friction of managing many personal conversations across many platforms is real, and none of them let a third-party tool participate cleanly. Every "AI assistant" you see in the wild either lives inside one platform (Meta AI, WhatsApp Business API bots) or is a browser extension that reads over your shoulder. Both approaches force compromises:

• Platform-internal assistants can't cross platforms. They also can't be configured per-contact — you can't tell one AI "always be concise with mom" while another AI "always confirms twice with the plumber before scheduling".
• Browser extensions can't run 24/7. They also can't act autonomously — they just draft; you must sit there to approve.

Mediator solves both by running as an independent service that authenticates to each platform the way a legitimate client does (WhatsApp Web pairing, Messenger MQTT session), keeps the state server-side, and hands per-contact context to the AI provider you choose. It's your accounts, your API key, your prompts. The app is the plumbing.

The design puts you in the middle of every decision the AI makes: the mediator has explicit REPLY / MARK / REACT / WAIT / CALL_TOOL / UPDATE_MEMORY actions rather than a free-form "do whatever" prompt, and every action is visible in the admin panel as it happens. If the AI wants to reply, you see it reply. If it wants to wait for you to confirm before sending a message, it shows up in a WAITING state. Nothing is a black box.