{"version":"2.1.290","anchor":"cloud-error-messages-are-sanitized","canonical_anchor":"cloud-error-messages-are-sanitized","heading":"Error messages from the cloud service are filtered and read more consistently","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-error-messages-are-sanitized","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Error messages from the cloud service are filtered and read more consistently\n\nCloud service errors now hide long or odd server text, ignore generic messages, and point you to --debug for the raw response\n\n**What**\n\nWhen a request to the cloud service fails, the error you see is now built more carefully:\n\n- Unsafe text is hidden: a server message that is too long or contains unusual characters or spacing is no longer shown. The message says to run again with `--debug` to see it. Session ids in error text that look malformed appear as `[not shown]`. Before, the raw server message was shown.\n\n- One shared way of reading errors: a failed move of a session to the cloud now takes its error text from a shared extractor, and the generic response-error formatter uses the same one. A generic \"The request was invalid.\" message is ignored in favour of the fallback text, which still says to run with `--debug` to see the raw response.\n\n`--debug` starts Claude Code in debug mode, which shows extra detail.\n\n**Why**\n\nOdd or overlong text from a server can no longer mess up your terminal display, and errors read the same way across cloud features. If a message is hidden, `--debug` is where to find the full text.\n\n- Area: Cloud Sessions\n- Names: `--debug`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}