# Editable agent send policy | Changelog

Source: https://wraps.dev/changelog/editable-agent-send-policy

![Wraps Logo](https://wraps.dev/wraps-light-logo.png)![Wraps Logo](https://wraps.dev/wraps-dark-logo.png)

](https://wraps.dev/)

[](https://github.com/wraps-team/wraps)[Log in](https://app.wraps.dev/auth?mode=signin)[Sign up](https://app.wraps.dev/auth?mode=signup)

Toggle menu

[← All changes](https://wraps.dev/changelog)

CLIAPIAgentsSeptember 2026

### Editable agent send policy

Change an agent mailbox's send caps and recipient allowlist after it is created, without recreating the agent.

-   Run `wraps email agent policy <name>` to change a live agent’s policy. `--max-per-hour` and `--max-per-day` set the caps, `--allow-recipient` and `--allow-domain` add to the allowlist and can be repeated, and `--clear-allowlist` empties it. Fields you leave out keep their current values. The API equivalent is `PATCH /v1/agents/:id/policy`. A killed agent’s policy cannot be changed
-   `wraps email agent create` checks the domain for an MX record and warns when replies to the new address will bounce. Set `replyTo` on every send to a mailbox that can receive, or run `wraps email inbound` so the domain accepts mail
-   Pass `--org <slug>` to `wraps platform connect` to pick the organization without a prompt, so the command runs in CI. With more than one organization and no `--org`, a `--yes` or `--json` run exits with an error rather than choosing one. `wraps platform update-role` now honors `--yes`
-   Fix: if a deploy failed with advice to check your AWS permissions after an earlier run was interrupted, the error now names the pending Pulumi operations and tells you to run `pulumi refresh`

Also fixed (2)

-   wraps platform update-role says when it left the trust policy untouched because no external ID is stored, and tells you to re-run wraps platform connect.
-   wraps --version reports the new version after wraps update, and update no longer re-offers a release you already installed.

CLI v3.12.0