{"version":"2.1.287","anchor":"bash-cd-then-read-approval-message-differs-for-cloud-session","canonical_anchor":"bash-cd-then-read-approval-message-differs-for-cloud-session","heading":"Cloud sessions explain why a cd-then-read Bash command needs approval","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/bash-cd-then-read-approval-message-differs-for-cloud-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud sessions explain why a cd-then-read Bash command needs approval\n\nIn cloud sessions, the approval prompt for a Bash command that changes folder then reads a file now explains the key and sign-in file risk\n\n**Unclear.** What decides that a session counts as a cloud session here is not stated.\n\n**What**\n\nWhen a Bash command changes folder with `cd` and then reads a file by a relative path, Claude Code asks you to approve it. Before, the prompt only described the `Read()` deny rule.\n\nIn cloud sessions, the prompt now says the read cannot be checked against this computer's keys and sign-in files before it runs, and that a cloud session may not read them.\n\n**Why**\n\nIn practice, people approving this kind of command in a cloud session now see why it was stopped.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}