| name | microsoft |
| description | Use for any Microsoft account, personal or work (Outlook.com, Hotmail, Live, Microsoft 365); preferred over email-client for Microsoft accounts. Graph-based mail (read/send/reply/forward, drafts, flag/categorize, move/archive, folders, attachments, block senders), calendar and meetings, Microsoft Teams (chats, channels, presence), and new-mail/Teams notifications. Requires daemon. |
Microsoft - CLI: microsoft
Setup / sign-in: run microsoft auth setup --account <email>, one command provisions mail, calendar, and Teams and auto-picks device-code (personal / permissive) or a one-URL browser sign-in (locked work/school tenants), then auto-refreshes so the user signs in only once. Details and the two backends (Graph + browser-capture fallback): see SETUP.md.
Background daemon: screen -dmS microsoft microsoft serve --notifications-dir ~/agent/notifications
Command groups
Each area's detail lives in its own file, read it when you work in that area:
- Email: read/send/reply/forward, search, organize (flag/categorize/move/archive), drafts, folders, block/unblock, attachments. See references/email.md.
- Calendar: list/create/update/respond to events and meetings. See references/calendar.md.
- Teams: chats, channels, presence (and Teams sign-in). See references/teams.md.
- Notifications: new-mail folder watching + Teams chat alerts (plus non-interrupting Teams channel alerts where the account has channel access; degrades to chats-only otherwise). See references/notifications.md.
Shared flags
--account <email> is required on every email/calendar/folder/teams command (list accounts with microsoft auth list; sign one out with microsoft auth remove --account <email>).--backend {auto,graph,owa-rest} (default auto) picks the path; both backends support the full surface except block/unblock (Graph-only). See SETUP.md.- List commands (
email list/search, calendar list/calendars, folder list, teams chats/messages/teams/channels) default to a compact tab-separated table; pass --json for one-line JSON or --json-pretty for indented JSON. Graph @odata.* metadata is stripped from every result.
Draft-only mode
Set EMAIL_DRAFT_ONLY=1 (truthy: 1/true/yes, case-insensitive) to hard-disable sending. In this mode email send/reply/forward are refused before any Graph or OWA-REST call (non-zero exit with a clear message); only email draft works. This is a CLI-level safety guarantee, not a behavioral promise, and it covers both backends. Default off: unset/empty means today's behavior, no change.
Personalization
Threaded reply DRAFT (leave unsent for the user to send)
email reply ALWAYS sends and email draft --reply-to overwrites the quoted history. To leave a
threaded reply(-all) draft the user reviews + sends themselves, use email reply-draft
(createReply/createReplyAll + body placed above the preserved quote + attach, no /send):
microsoft email reply-draft --account user@example.com --id '<latest-msg-id-in-thread>' --body "draft answer for review"
microsoft email reply-draft --account user@example.com --id '<email_id>' --body "thanks all" --reply-all --attachments /path/file.pdf
--body is plain text (- lines become bullets), placed above the quoted thread. On a re-edit
pass --replace-draft <old_id> (the id printed by the prior run) so repeated tweaks leave
exactly one draft, not a pile. Graph-only.
Contact Communication Styles
[How to communicate with different contacts. Fill in after data gathering: who are the key contacts, what tone/formality for each, language preferences]
Email Preferences
[User's email patterns. Fill in after data gathering: greeting style, sign-offs, capitalization, punctuation habits, typical length, tone, which account for what]
Cold-email screening (optional standing behavior)
If the user asks you to screen their inbox, watch new-mail notifications for cold 1:1 outreach: unsolicited investor/VC pitches, recruitment/mentor solicitations, sales/SaaS/agency prospecting, cold "let's chat" intros. For these:
- Move the message to a
Screened folder on that account (microsoft email move --account X --id <id> --to-folder Screened) so it leaves the inbox, and drop the notification (never surface it).
- Never delete the Screened folder is a holding area the user can skim anytime; nothing real is lost.
- When unsure, leave it in the inbox (conservative: a genuine warm intro, a real deal, or anything from a known contact stays and gets surfaced normally). Better to leave one cold email than misfile a real one.
- Repeat offenders → block the sender (
microsoft email block --account X --sender ..., Graph-only).
- Create the
Screened folder once per account (microsoft folder create --account X --name Screened). Newsletters and marketing are usually better left in the inbox unless the user asks to file those too.
Scheduling Preferences
[User's scheduling patterns. Fill in after data gathering: preferred meeting times, timezone, how they reschedule, buffer preferences]
Regular Events
[Recurring meetings and commitments. Fill in after data gathering: weekly/monthly recurring events, who with]
