Add MCP prompts (catch-up, daily-digest)

[toloco]

No WhatsApp MCP server exposes prompts yet. Templates like catch-up ('summarize what I missed in chat X'), daily-digest, reply-suggestion. mcp-go supports server.AddPrompt(). This is a differentiator.

[m13v]

prompts are the easy bit. the hard part is clean message data underneath. last time i worked on catch-up over accessibility reads, unread count lied constantly (WhatsApp marks preview reads), and scrolling past ~50 started returning duplicates when chunks reloaded. timestamps also come back as 'yesterday' or '2:30 PM' with no date anchor, so you need a separate normalization pass. templates feel great in demos and fall apart on a group with 200+ msgs since monday. how are you sourcing the raw window?

[toloco]

Good questions — but whasapo doesn't read the WhatsApp UI at all. We connect directly to the WhatsApp multi-device protocol via whatsmeow (same protocol the official apps use).

So the issues you're describing don't apply here:

• Timestamps are Unix epoch from the protobuf — exact to the second, no "yesterday" or "2:30 PM" normalization needed
• Deduplication is handled by SQLite primary key (id, chat) — messages are inserted with ON CONFLICT DO UPDATE
• Unread counts — we don't use them. Every message is stored as it arrives via event handlers + history sync on first connect
• Scrolling/chunks — no UI scraping. HistorySync events deliver past messages in bulk on pairing, and live messages come through events.Message

We currently have 16k+ messages in SQLite with indexed queries. The raw data for prompts is clean structured rows: id, chat, sender, push_name, text, timestamp, is_from_me, is_group, media_type.

The prompt templates would just be SQL queries + formatting — e.g. "catch-up" = SELECT * FROM messages WHERE chat = ? AND timestamp > ? ORDER BY timestamp passed to the LLM with context.