{"version":"2.1.290","anchor":"bridge-redacts-transcriptsdk-events-and-keeps-account-memor","canonical_anchor":"bridge-redacts-transcriptsdk-events-and-keeps-account-memor","heading":"Remote Control no longer receives account memory prompts","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bridge-redacts-transcriptsdk-events-and-keeps-account-memor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote Control no longer receives account memory prompts\n\nAccount memory prompts now stay in the terminal instead of going to Remote Control, and outgoing events pass through a redaction step\n\n**Unclear.** It is not clear what the redaction step removes.\n\n**What**\n\nRemote Control lets you follow and steer a Claude Code session from another device. Two things change in what Claude Code sends to it:\n\n- Every outgoing event now passes through a redaction step, which hides some content, before it is sent.\n\n- A prompt asking about account memory now stays in the terminal and is no longer sent to Remote Control. Any answer or cancel for it that comes from Remote Control is ignored.\n\nBefore, such requests were passed on without this check.\n\n**Why**\n\nAccount memory prompts can only be answered at the terminal, and event content is cleaned before it leaves your machine.\n\n- Flag `tengu_bridge_requires_action_details`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.290; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}