pidge 1.5.0

Your AI agent already writes your code. pidge lets it handle the rest of your day too: triage the inbox, draft replies, find a free slot, book the meeting and answer the invite, across every mailbox you have, from one tool.

You:    Go through my unread mail, archive the newsletters, and draft a reply to
        Bob proposing a slot next week when we're both free.

Agent:  $ pidge mail list --unread --json
        $ pidge mail archive 3f1a
        $ pidge mail archive 9c02
        $ pidge calendar --week --json
        $ pidge mail reply 4d8e --draft --body-file -
        Archived 2 newsletters. Drafted a reply to Bob proposing Tue 14:00 or
        Thu 10:00. Want me to send it?

Why pidge

• Built for agents first. Every command speaks --json, messages and events have short stable ids, lists page with cursors, and mail delta / calendar delta / pidge watch let long-running agents follow changes instead of re-reading everything.
• You stay in control. Sends ask before they go, and agents can save drafts for you to approve. Lock things down further with per-action guardrails (pidge config set guardrails.send confirm, also delete, cancel, rsvp, bulk, unsubscribe; each allow / confirm / deny) or preview anything with --dry-run. The MCP server goes further: sends only from an approved draft, a per-user send cap, and third-party mail content marked as untrusted so your agent summarises it instead of obeying it.
• All your mailboxes in one view. Sign in to several accounts; reads are merged across all of them, and writes go out from the right one.
• Mail and calendar in one tool. Search, read, reply, forward, file, unsubscribe; create, reschedule, duplicate, cancel and RSVP to events, including recurring meetings.
• Fast and self-contained. A single Rust binary. Tokens live in your OS keychain.

Get started

Option 1: CLI + agent skill (Claude Code, Codex, Copilot, …)

brew install mklab-se/tap/pidge        # or: cargo install pidge (see INSTALL.md)
pidge account add                      # sign in (opens your browser)
pidge ai skill --emit > ~/.claude/skills/pidge/SKILL.md

That's it, ask your agent about your mail. The emitted skill is deliberately small: it teaches the agent the patterns (JSON output, confirmation gates, account context) and points it at pidge --help for everything else, so it keeps working as pidge grows.

Option 2: Remote MCP server (Claude.ai, ChatGPT, Cowork, …)

For harnesses that speak MCP rather than run shell commands, pidge-mcp exposes the same mail and calendar tools over HTTP. Each user signs in with their own account and only ever sees their own mailboxes.

• Self-host it: a ready-made image is published at ghcr.io/mklab-se/pidge-mcp, with Bicep templates for Azure Container Apps.
• The reference server at https://pidge.mklab.se/mcp is currently invite-only.

See docs/mcp.md for connecting clients, self-hosting, and moving an existing local setup over with pidge mcp connect.

Using it yourself

pidge is a pleasant CLI for humans too:

pidge mail                                   # latest mail, all accounts
pidge mail 3515                              # open a message by id fragment
pidge mail search 'from:alice subject:budget'
pidge calendar --week                        # the week ahead
pidge calendar new --title "Q3 planning" --start "tomorrow 15:00" --end "+90m" \
  --invite alice@example.com --online

More in docs/usage.md, or run pidge --help.

Supported providers

Microsoft 365 work/school accounts and personal Microsoft accounts (Outlook.com, Hotmail, Live) today. pidge's core is provider-neutral, and more providers may follow.

Contributing

See CONTRIBUTING.md and DEVELOPMENT.md. Changes are listed in CHANGELOG.md, newest first.

License

MIT, see LICENSE.