Changelog

Notable changes to the agent packages: AgentSkill, the MCP servers, presets and integrations. The source of truth is CHANGELOG.md in the repository; this page mirrors it.

3 Nov 2026

v0.3.331 added · 2 changed

Meeting invitations. Agents can schedule meetings by email: atomicmail calendar send|update|cancel|list|respond in the CLI, and the send_invite, update_invite, cancel_invite, list_invites and respond_to_invite tools in the local MCP server (the hosted MCP server has them too). Guests get a standard invitation with Yes / No / Maybe in Gmail, Outlook and Apple Mail, and their answers come back to the inbox. An invitation can carry a video-call link and can be all-day; up to 25 guests. New help topic calendar and docs page Calendar invitations. TypeScript packages only for now.
Recipient limits. One message can address up to 50 recipients (to + cc + bcc; more on paid plans), and each inbox has a daily recipient limit. Over a limit the send is refused with tooManyRecipients: split the message or try the next day.
Mail from @atomicmail.ai inboxes now ends with "Sent from Atomic Mail Agentic".

AddedChanged

30 Oct 2026

v0.3.322 added · 1 fixed

Webhooks. Inbox owners can now get a signed POST for every new message in an agent inbox instead of polling it. Endpoints are set up in the dashboard by an owner who signs in with Google or GitHub; requests follow Standard Webhooks v1. The new Webhooks page covers setup, signature verification (Node.js and Python), how to connect a webhook to your agent, local testing, retries and limits. The clients in this repo do not change: your agent keeps reading mail the same way, and the webhook tells it when to look.
Cursor plugin manifest, so Atomic Mail Agentic can be listed in the Cursor Marketplace.
The skill launcher is now invoked through bash, so a lost executable bit (for example after a zip download) no longer breaks the skill.

AddedFixed

27 Sep 2026

v0.3.311 security · 3 fixed

Python clients now JSON-escape $VAR values. langchain-atomicmail, pydantic-ai-atomicmail and the Dify plugin substituted $VAR values into the JMAP JSON unescaped, so a crafted inbound subject could add method calls to a reply.json batch (reachable since 0.3.30). Values are now escaped in string context, like the TypeScript runtime. Python callers who pre-escaped values (for example \n for a newline) should now pass raw text.
reply.json picks its recipient like the hosted MCP server (first usable Reply-To, else From, else Sender) and replies to that one address only. Line breaks in the subject collapse to a space and an existing Re: is kept.
Send examples in help and the docs now file the sender's copy in Sent and clear $draft on success, like the bundled presets.

SecurityFixed

27 Sep 2026

v0.3.302 fixed · 1 changed · 2 added

Sent mail no longer stays a draft in the inbox. The send presets (send_mail.json, send_mail_attachment.json, send_mail_blob_attachment.json, reply.json) now file the sender's copy in Sent and clear $draft once the message is submitted, so it is marked $sent instead of looking unsent. Accounts without a Sent mailbox keep using the inbox.
reply.json sends again, in the same thread. The server rejected it with invalidProperties, so no reply ever went out. The client now looks up the original by MAIL_ID and replies to its Reply-To (else From), with Re: and inReplyTo set. Inputs are unchanged (MAIL_ID, BODY), so the n8n and Dify reply actions work too.
list_inbox.json shows only mail that arrived; the agent's own sent mail is no longer mixed in. Read it with list_sent.json.

FixedChangedAdded

23 Sep 2026

v0.3.291 fixed

Make skill SKILL.md transform tolerant of the npx package name

Fixed

23 Sep 2026

v0.3.281 changed · 4 docs

Add Pydantic AI integration package (port of #59 to main)
Redesign docs.atomicmail.ai + SEO (canonical, OG, sitemap, llms.txt)
Clean URLs + serve /index.md for agents (follow-up to #56)

ChangedDocs

18 Sep 2026

v0.3.271 changed · 4 docs

Add hosted remote to server.json
Sibling-repo wiring, required watch param, daily cadence, custom-domains + API-key connect pages
Add custom domains & dashboard section

ChangedDocs

7 Aug 2026

v0.3.265 added · 5 changed

Required watch parameter on register ("scheduled" | "on-demand"), enforced in the MCP tool and the skill CLI wrappers only — it never reaches session.register(). Registration cannot complete without an operator-supplied value, turning "set up a recurring inbox check" from a request an agent can skip into a precondition it must resolve with its operator.
Per-host schedule setup on watch="scheduled". The calling runtime is detected from environment-variable markers (CLAUDECODE, OPENCLAW_HOME, HERMES_SESSION, ATOMIC_AGENT, CURSOR_*) — never from PATH — and register prints that host's own scheduler step: openclaw cron add …, hermes cron create …, or a Claude Code local-routine instruction. OS-level scheduling (cron/launchd/systemd) is deliberately never generated.
Scheduled-job prompt bakes in a literal --credentials-dir (scheduled sessions inherit no environment), a per-inbox job name (atomicmail-inbox-<user>) so multiple inboxes cannot collide, and least-privilege tool-allowlist guidance.