{"version":"2.1.288","anchor":"cloud-permission-line-distinguishes-asked-from-blocked","canonical_anchor":"cloud-permission-line-distinguishes-asked-from-blocked","heading":"Cloud permission log can now say a request was asked instead of blocked","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-permission-line-distinguishes-asked-from-blocked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud permission log can now say a request was asked instead of blocked\n\nThe cloud session permission log line now ends in asked for some answers, where it always said blocked before\n\n**Unclear.** It is not clear exactly which answers are logged as asked.\n\n**What**\n\nIn cloud sessions, Claude Code writes a log line for each permission check. That line used to always end in \"blocked\" followed by how long the check took. It now ends in \"asked\" for some answers and still says \"blocked\" for the rest.\n\n**Why**\n\nThe log is less misleading when a permission was passed to you to decide rather than denied.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}