{"version":"2.1.242","anchor":"computer-use-caps-what-claude-can-be-granted-per-app-class","canonical_anchor":"computer-use-caps-what-claude-can-be-granted-per-app-class","heading":"Computer use caps what Claude can be granted per app class","tier":"notice","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/computer-use-caps-what-claude-can-be-granted-per-app-class","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Computer use caps what Claude can be granted per app class\n\nBrowsers can only be seen, terminals only clicked, and Claude's own app never granted.\n\n**What**\n\nWhen Claude asks for control of an application, browsers can now only ever be granted see-only access, terminals and IDEs only clicking (no typing or pasting), and Claude's own application can never be granted at all, because that would let the model change its own permissions.\n\n**Details**\n\n- Browser refusals point the model at the Claude in Chrome extension MCP for actual interaction; terminal and IDE refusals point it at Bash.\n- Browser and terminal refusals allow one re-request in the same turn, confirmed once, and that allowance expires at the end of the turn.\n- First-request warnings can be turned off ahead of time with skipFirstRequestWarnings.\n\n**Evidence**\n\n`You requested access to Claude's own application.`\n\n- Area: Computer Use\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}