{"version":"2.1.248","anchor":"remote-control-startup-and-file-staging-failures-reply-with-","canonical_anchor":"remote-control-startup-and-file-staging-failures-reply-with-","heading":"Remote Control startup and file-staging failures reply with generic text","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-control-startup-and-file-staging-failures-reply-with-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote Control startup and file-staging failures reply with generic text\n\nRemote Control startup and staging failures now reply with generic text and log the reason.\n\n**What**\n\nWhen Remote Control fails to start, the reply is now \"Remote Control initialization failed\" rather than the raw internal reason, and the reason is recorded to telemetry first. Staging a file does the same. Reads, plan fetches, workspace diffs and file suggestions now reply through a reporter tagged with the request name instead of stringifying the exception, and an unknown request subtype is escaped before it is echoed back.\n\n**Evidence**\n\n`Remote Control initialization failed`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}