{"version":"2.1.293","anchor":"remote-io-diagnostics-carry-a-reason-code","canonical_anchor":"remote-io-diagnostics-carry-a-reason-code","heading":"Remote session problem reports now include a reason code","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remote-io-diagnostics-carry-a-reason-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remote session problem reports now include a reason code\n\nDiagnostic reports from remote sessions now carry a reason code, and two new steps run on user messages and file-staging requests\n\n**Unclear.** What the two new steps for user messages and file-staging requests actually do is not shown.\n\n**What**\n\nWhen something goes wrong with the connection behind a remote session, Claude Code produces a diagnostic report (a technical note about the problem). These reports now include a reason code alongside the message and its severity. Examples are `transport_closed_permanently` and `worker_registration_failed`.\n\nClaude Code also now runs two new steps when a message arriving over this connection is either a message from the user or a request to stage a file (prepare a file to be sent into the session).\n\n**Why**\n\nReports about remote session problems now say more precisely what went wrong. The change also touches how incoming user messages and file staging are handled in remote sessions.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}