Inbox, calendar, and life operations

Personal operations people describe as “it found the PDF in my email” or “inbox zero from WhatsApp”:

• Search and triage across mail and attachments with explicit scopes.
• Calendar-aware prep: agendas, travel time, conflicts—grounded in what the calendar actually says.
• Task and project hygiene: capture, defer, delegate—without losing context between sessions.
• Life admin (forms, reimbursements, appointments) as checklisted workflows, not one-shot magic.

CoWork OS does not replace your judgment on sensitive life decisions—it reduces friction on repeatable steps.

• Persistent context and graph-style memory (where configured) reduce “start from zero” every morning.
• Channels meet you on mobile or desktop messengers.
• Local-first / BYOK options align with mail and calendar data sensitivity.
• Approvals before sending email or submitting forms on your behalf.

1. Segment mail and calendar access: work vs personal vs shared family.
2. Start with read and summarize; escalate to draft only after accuracy checks.
3. Use fixed templates for outbound messages you send often.
4. Never fully automate financial or legal commitments without human send.
5. Review weekly: what did the agent get wrong, and why?

• Clear policies for what may be summarized vs quoted vs acted on.
• 2FA and token hygiene for connected accounts.
• Backup path when OAuth breaks (expired refresh tokens).

1. Connect one source (e.g. calendar read-only).
2. Build two trusted summaries: daily plan and weekly review.
3. Add email search with narrow folders or labels first.
4. Introduce drafts with mandatory preview.
5. Expand to life admin checklists one category at a time.

• “Summarize only threads labeled X from the last 7 days.”
• “List conflicts tomorrow without suggesting solutions yet.”
• “Draft a reply that asks for missing info—does not assume it.”

• Spot checks show correct dates, names, and amounts on real data.
• You can revoke access in under five minutes.
• Family or colleagues know what the assistant may and may not do.

• Hallucinated meeting times—always verify against the calendar UI.
• Forwarding sensitive threads to the wrong channel.
• Over-automation of relationship-sensitive email.
• Storing PII in places that break retention policy.