{"version":"2.1.248","anchor":"bridge-sessions-get-trimmed-control-replies-and-generic-erro","canonical_anchor":"bridge-sessions-get-trimmed-control-replies-and-generic-erro","heading":"Bridge sessions get trimmed control replies and generic errors","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/bridge-sessions-get-trimmed-control-replies-and-generic-erro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Bridge sessions get trimmed control replies and generic errors\n\nBridge and cloud sessions get trimmed control replies with local detail and errors removed.\n\n**What**\n\nWhen Claude Code runs as a bridge or cloud session, several control replies drop local machine detail: context usage returns an empty memory-files list, file rewind omits the list of files changed, usage omits behaviours, and rewind or event-poll failures come back as fixed texts such as \"Failed to rewind\" rather than the underlying error.\n\n**Details**\n\n- Gated on the environment, not remote config: it applies when `CLAUDE_CODE_ENVIRONMENT_KIND` is `bridge` and the transport persists.\n- Outside that mode the real error text and full payloads are returned as before.\n\n**Evidence**\n\n`a.CLAUDE_CODE_ENVIRONMENT_KIND === \"bridge\"`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}