@agentcomms/resend 0.7.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Criss Moldovan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,112 @@
+# @agentcomms/resend
+
+Resend for coding agents. Read a team's domains, sent and received mail, metrics and suppressions — and send email
+that **nothing sends without a person's approval of exactly what goes out**, once.
+
+```sh
+npm install -g @agentcomms/resend    # or run it with npx @agentcomms/resend <command>
+```
+
+New in 0.7.0.
+
+## What it promises, and who enforces it
+
+**Read-only is enforced by this package, not by the key.** Resend has no read-only API key. A full-access key can
+read, send, delete domains and create keys; an account in `read` mode is kept from sending by this package's own
+code, but the key itself would not stop anything else that held it. A sending-only key can only send — Resend
+enforces that — and it cannot read anything, so reads with it are reported as unavailable. `agent-resend doctor`
+says this on every run.
+
+**Nothing is sent without a person.** A send is prepared, previewed — every recipient, BCC included, the reach
+(unique recipients), the From domain and whether it is verified — and approved: a yes in the conversation under the
+account's `chat` policy, or `agent-resend approve <id>` and a typed code under `confirm`. Above ten recipients, or to
+an address that arrived in mail read here, a person at a terminal approves, whatever the policy. The approval id is
+the request's `Idempotency-Key` and an `agentcomms_approval` tag; a send whose outcome is unknown is never repeated,
+only checked.
+
+**The key is typed by a person, at a terminal.** `agent-resend account add` reads it from a hidden prompt, or from
+`RESEND_API_KEY` in that terminal, and stores it in the system keychain. No MCP tool accepts a key: a key typed into
+a chat stays in the transcript.
+
+**Received mail is untrusted.** Bodies, subjects, names and attachment names arrive inside the untrusted-content
+envelope with hidden text removed and counted, beside Resend's own SPF, DKIM and DMARC results. Attachments are
+listed, and downloaded only when asked, into the downloads folder.
+
+**It stays out of the way of the team's own mail.** Resend's rate limit is shared by every key of a team, and
+Resend does not say which team a key belongs to, so this package asks at most twice a second from a computer in all,
+whichever account asks, and a 429 through any account stops every account until Resend says it may ask again.
+
+It never manages domains, API keys, webhooks, broadcasts, contacts or audiences, from any surface.
+
+## Getting started
+
+A person connects an account at their own terminal, then registers the server with their agent:
+
+```sh
+npx -y @agentcomms/resend account add acme/resend               # type the key when asked; read mode by default
+npx -y @agentcomms/resend mcp install --client claude-code      # a registration you approve
+```
+
+`--client` also takes `codex`, `cursor`, `gemini`, `claude-desktop`, `vscode` and `json`. Add `--account
+acme/resend` to pin the server to one account. From a chat with the core server connected, `comms_server_install`
+with `channel: "resend"` makes the same registration, and either one's approval is good for the other.
+
+```sh
+agent-resend doctor
+agent-resend domains --account acme/resend
+agent-resend received list --account acme/resend
+agent-resend account policy acme/resend --mode send   # a change a person approves
+agent-resend send prepare --account acme/resend --from "Acme <hello@acme.test>" --to sam@partner.test \
+  --subject "Hello" --text "Hi Sam"
+```
+
+## Accounts
+
+An account is one Resend API key for one team, named `organisation/resend`. It lives in the one agent-communications
+configuration beside every mailbox and workspace, so `agentcomms names migrate`, `agentcomms secrets migrate` and
+`agentcomms policy --account <name>` treat it like any other; its key is in the one secret store under
+`resend:key:<id>`.
+
+Its mode is `read` or `send`. Moving it to `send`, loosening its send policy (`chat`, `confirm`, `never`) or its
+change policy (`chat`, `confirm`), and removing it are **change approvals**: a preview, and nothing until a person
+agrees — in the conversation under the `chat` change policy, at their own terminal under `confirm`. Tightening
+applies at once.
+
+## Commands and tools
+
+Every command has an MCP tool running the same operation, except three: `account add` (a key is typed at a
+terminal), `approve` (under `confirm`, a person at a terminal) and `mcp` (it starts the server).
+
+| Command | MCP tool |
+|---|---|
+| `agent-resend account add <name>` | — typed at a terminal |
+| `agent-resend account list` | `resend_accounts_list` |
+| `agent-resend account show <name>` | `resend_account_show` |
+| `agent-resend account policy <name>` | `resend_account_policy` |
+| `agent-resend account remove <name>` | `resend_account_remove` |
+| `agent-resend doctor` | `resend_doctor` |
+| `agent-resend domains` | `resend_domains` |
+| `agent-resend emails list` | `resend_emails_list` |
+| `agent-resend emails show <id>` | `resend_email_show` |
+| `agent-resend received list` | `resend_received_list` |
+| `agent-resend received show <id>` | `resend_received_show` |
+| `agent-resend received download <id>` | `resend_received_download` |
+| `agent-resend metrics` | `resend_metrics` |
+| `agent-resend suppressions` | `resend_suppressions` |
+| `agent-resend send prepare` | `resend_send_prepare` |
+| `agent-resend send execute <approvalId>` | `resend_send_execute` |
+| `agent-resend send status <approvalId>` | `resend_send_status` |
+| `agent-resend scheduled list` | `resend_scheduled_list` |
+| `agent-resend scheduled cancel <id>` | `resend_scheduled_cancel` |
+| `agent-resend approve <approvalId>` | — a person at a terminal |
+| `agent-resend mcp` | — it starts the server |
+| `agent-resend mcp install --client <client>` | `comms_server_install` (core) |
+| `agent-resend mcp prune` | `comms_server_prune` (core) |
+
+Every command takes `--json` for the whole result, with stable exit codes: `0` ok, `10` a send or a change was
+refused or needs approval, `64` usage, `65` bad data, `66` not found, `69` Resend or the secret store unavailable,
+`75` temporary, `77` key or permission needed, `78` configuration problem.
+
+The skills `resend-reading` and `resend-sending` teach an agent to use them. Everything else — the other channels,
+the design and the reference pages for every command and tool — is in
+[the repository](https://github.com/crissmoldovan/agent-communications).