[FEATURE] Full control for browsers
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Hi there, I'm a Shopify app developer and use Claude Desktop's computer-use MCP to run automated end-to-end tests on my Shopify apps.
That was working perfectly until I upgraded my Claude Desktop to v1.3109.0 where computer-use tier policy was tightened so that all browsers are capped at tier "view only" (clicks and typing blocked; only screenshots allowed), per the documentation at https://code.claude.com/docs/en/desktop#app-permissions.
The recommended alternative — the Claude-in-Chrome extension — does not work for my use case because the Shopify admin embeds app UI inside a cross-origin iframe (shop admin hosted on admin.shopify.com, app UI hosted on myownserver.com). Chrome MCP's computer tool dispatches CDP events against the top frame's target only, so clicks and typing targeted at iframe coordinates focus the <iframe> host element but do not propagate into the iframe's out-of-process document. I verified this empirically:
- Click at iframe-input coordinates: focus transfers to the <iframe> element in the top frame (document.activeElement.tagName === "IFRAME") but the input inside the iframe never focuses.
- Subsequent typing: reaches the iframe's <body> (a space keystroke scrolls the iframe body) but never reaches the focused input element inside the iframe.
Proposed Solution
Move this option to settings, so users can configure View only / Click only / Full control for the browser
Alternative Solutions
No real alternative
Priority
Critical - Blocking my work
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗