Goal: Connect to email and surface summaries in daily briefings.
File / Feature
Details
Owner
Status
Email connection
Connect to email via IMAP or Gmail API
opus
—
Daily email summary
Email summary in briefing
opus
—
Phase 2: Email Actions —
Goal: Enable Opus to draft and manage email responses.
File / Feature
Details
Owner
Status
Draft responses
Draft email responses via Opus
opus
—
Flag/categorize
Flag and categorize messages
opus
—
Phase 3: WhatsApp —
Goal: Integrate WhatsApp messaging into Opus.
Reference approach (proven implementation, see REBUILD_PROMPT):
whatsapp-web.js (Puppeteer) as bridge — no Business API needed
Separate wa-daemon process keeps a WhatsApp Web session alive
Outgoing messages queue in SQLite, daemon picks up and sends
Incoming messages trigger a notification
First run requires scanning a QR code in the terminal
Free — uses your existing WhatsApp account
Note: Command routing and batch decision parsing are defined in FR-022 (Phone Access) and should be reused for WhatsApp — not duplicated. The same routing layer that handles Telegram commands applies to WhatsApp messages.
File / Feature
Details
Owner
Status
Read access
Read access to WhatsApp messages
opus
—
Session mapping
Each WhatsApp chat maps to a Claude Code session ID in SQLite. /newchat clears the mapping. See session-mapping-pattern.
opus
—
Command routing
Reuse FR-022 command routing layer for WhatsApp messages
opus
—
Batch decision parsing
Reuse FR-022 batch decision parser for WhatsApp replies
opus
—
Response drafting
Draft WhatsApp responses
opus
—
Notification forwarding
Forward notifications to Opus
opus
—
Prerequisites / Gap Analysis
Requirements
Requirement
Description
REQ-1
Daily briefing includes email summary
REQ-2
Can draft an email response via Opus
Current State
Component
Status
Details
Email integration
—
No API connection exists
WhatsApp integration
—
No API connection exists
Gap (What’s missing?)
Gap
Effort
Blocker?
Email API setup
Med
No
WhatsApp API/bridge
High
No
Privacy/permission design
Med
No
Test
Manual tests
Test
Expected
Actual
Last
Fetch email summary
Returns unread email count and subjects
pending
-
Draft email response
Generates draft for user review
pending
-
Read WhatsApp messages
Returns recent messages
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-02-26
Created
Created from brain dump
2026-02-27
Renumbered
From FR-062 to FR-023
2026-02-28
Rewritten
Aligned to feature-request template
2026-03-04
Updated
Referenced FR-022 for command routing and batch decision parsing
References
MCP servers for Slack/Discord/email could simplify integration