{"version":"2.1.301","anchor":"remote-session-failure-notices-are-flagged-and-their-text-sa","canonical_anchor":"remote-session-failure-notices-are-flagged-and-their-text-sa","heading":"Remote sessions mark failure notices and clean up their error text","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/remote-session-failure-notices-are-flagged-and-their-text-sa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Remote sessions mark failure notices and clean up their error text\n\nFailure messages from remote sessions are now flagged and cleaned, runner errors are redacted, and cancelling records when the turn stopped\n\n**What**\n\nA remote session is Claude Code running on another machine while you watch or steer it from here. Several things about how it reports problems changed:\n\n- Messages from Claude that match a session-failure notice are now marked `sessionFailureNotice: true`, and their text is passed through a cleanup step before it is shown.\n\n- The tail of the runner's error output (stderr, where a program writes its errors) now goes through a helper before it is put into failure messages. This appears to redact it.\n\n- When you cancel, the published state now records `lastTurnStopTime`, the time the turn stopped.\n\n- Before connecting, startup now waits for a step that uses the session's SDK address (`sdkUrl`).\n\n- A message already marked `isApiErrorMessage` now counts as an API error, as well as one marked `is_api_error_message`.\n\nThe forwarding of plugins and hooks to remote sessions is unchanged.\n\n**Why**\n\nFailure messages from remote sessions can now be shown as failure notices instead of ordinary replies, and with less raw error output in them.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}