# One Doctor Command & Structured Remediations | Changelog

Source: https://wraps.dev/changelog/one-doctor-command-and-structured-remediations

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

CLIAugust 2026

### One Doctor Command & Structured Remediations

-   New `wraps doctor` merges the AWS and email doctors into one report and one exit code, with `--json` carrying remediations for MCP and agent callers. `wraps email doctor` is unchanged
-   Every finding now carries a structured remediation from one registry — the command that repairs it, rather than a hand-written sentence beside it. A single missing SES configuration set previously took a user five commands and a CLI reinstall, three of them because the CLI misdirected them. Checks with no automatic repair say so instead of guessing
-   Remediation commands carry the region the doctor actually scanned, so a pasted fix cannot fall back to `us-east-1` and report that the connection does not exist. `wraps aws doctor -r/--region` answers for a named region on both the human and `--json` paths
-   An unrecognized command is reported as bad input with the nearest routed command suggested, not as a crash
-   Fix: error telemetry is flushed before the process exits — it was being dropped. Event names no longer carry whatever you typed, error telemetry no longer ships raw error messages, and `wraps push` no longer puts the template slug in the payload
-   Fix: `wraps platform connect` and `wraps email upgrade` no longer print raw API error text
-   Fix: a failed Pulumi deploy exits non-zero instead of reporting success
-   Fix: the standalone binary ships on the Node version it claims to require

CLI v3.4.0