# Signed Reply-To Threading | Changelog

Source: https://wraps.dev/changelog/signed-reply-to-threading

![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)

CLIApril 2026

### Signed Reply-To Threading

-   `wraps email reply init --domain yourdomain.com` to enable cryptographic reply threading for agent workflows
-   Outbound: SDK accepts a `conversationId` option on `email.send` and returns `{ conversationId, sendId }`
-   Inbound: `email.received` now includes `replyToken: { status, conversationId?, sendId? }` and `autoReply: boolean`
-   HMAC secret stays in your AWS SSM Parameter Store — Wraps platform never sees it
-   Fix: `wraps email inbound init` now respects `--yes` and `--json` on the DNS confirmation prompt for CI scripting
-   See the [reply threading guide](https://wraps.dev/docs/guides/reply-threading)

CLI v2.19.0