{"version":"2.1.242","anchor":"each-per-app-tool-now-needs-a-specific-permission-tier","canonical_anchor":"each-per-app-tool-now-needs-a-specific-permission-tier","heading":"Each per-app tool now needs a specific permission tier","tier":"soon","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/each-per-app-tool-now-needs-a-specific-permission-tier","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Each per-app tool now needs a specific permission tier\n\nPer-app tools each require a permission tier, so a low grant lets Claude look but not act.\n\n**What**\n\nThe existing read, click and full permission tiers are mapped onto the individual per-app tools, so a low-tier grant permits looking but not acting. Calls below the required tier come back as tier_insufficient with guidance to request a higher tier.\n\n**Details**\n\n- Read tier: app_list_windows, app_screenshot, app_ax_find, app_batch, app_bring_to_current_space.\n- Click tier: app_click, app_scroll.\n- Full tier: app_drag, app_type, app_key, app_menu.\n- app_menu additionally refuses Services submenu items and Apple-menu system actions; app_key refuses key combinations that would touch the system clipboard.\n\n**Evidence**\n\n`tier_insufficient`\n\n- Area: Computer Use\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}