{"version":"2.1.290","anchor":"remote-call-relative-path-deny-and-a-remote-control-folder","canonical_anchor":"remote-call-relative-path-deny-and-a-remote-control-folder","heading":"Remote Control calls refused when a relative path cannot be confirmed","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-call-relative-path-deny-and-a-remote-control-folder","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote Control calls refused when a relative path cannot be confirmed\n\nA call can now be refused because its relative path could not be confirmed, and a notice explains cloud use of the folder\n\n**Unclear.** Where each message is shown, and what controls this behaviour, is not known.\n\n**What**\n\nTwo new messages relate to Remote Control, which lets a cloud session work with a folder on your machine:\n\n- A refusal: \"The call could not be confirmed after the answer, so it did not run.\" It applies when a call using a relative path (one written from the current folder, not from the top of the disk) cannot be confirmed.\n\n- A notice that cloud sessions can use this folder while Remote Control runs, and that commands needing approval ask in the cloud session first.\n\n**Why**\n\nThis changes how permissions work when a cloud session acts on your machine through Remote Control: approvals happen in the cloud session, and an unconfirmed call does not run.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}