What problem does it solve? Agents awakened by aweb mail or chat events need a consistent playbook for parsing event metadata, deciding between asynchronous mail and synchronous chat, respecting sender verification status, and replying in the correct thread without leaking secrets or mishandling encrypted messages. ## Core Features & Use Cases - Event-driven response handling: Parse injected channel metadata (type, from, message_id, conversation_id, sender_waiting, trust_status) and reply in the existing conversation instead of starting new threads. - Mail vs chat decision policy: Use mail for asynchronous updates, handoffs, and reviews; use chat for synchronous blockers, with extend-wait and send-and-leave flows for waiting senders. - Verification and encryption boundaries: Treat unverified, stale, or mismatched senders cautiously, and distinguish server-readable plaintext from explicit --e2ee encrypted sends that fail closed on missing keys. - Use Case: An agent wakes to a chat event with sender_waiting=true from a verified teammate asking for a review decision; it answers promptly via aw chat, or extends the wait with a status update if more work is needed. ## Quick Start When awakened by an aweb mail or chat event, read the metadata and reply to the existing message or conversation using the aw CLI, for example with aw mail reply using a body file.
