In March 2026 a developer opened a GitHub issue against Anthropic\'s public repository asking for official Safari extension support for Claude. Anthropic closed the issue with a single label: "not planned." For Mac users who prefer Safari to Chrome, that is the official answer, at least for now. Claude in Chrome is the only Anthropic-built browser extension, and there is no roadmap commitment to ship one for Safari.
The decision has caused some grumbling on Hacker News and Reddit. It also makes strategic sense when you look at it from Anthropic\'s product perspective. This piece walks through why the decision happened, what it tells you about Anthropic\'s priorities, and what the workaround looks like for Mac users who do not want to switch browsers.
The Chrome-first strategic logic
Anthropic\'s Claude in Chrome extension is in beta and limited to a controlled cohort of Claude Max subscribers, somewhere around 1,000 users at launch. The extension is not yet a general-availability product. Resources spent supporting it cover Chrome and Chromium-based browsers (Edge, Brave, Opera, Arc), which together represent more than 70 percent of global desktop browser market share.
Adding Safari support is not a small project. Safari has its own extension architecture (App Extensions, built on WebKit), its own developer ecosystem, its own distribution channel (the Mac App Store), and its own review process. Building, shipping, and maintaining a parallel Safari version of any browser extension is a significant engineering and operational commitment. For a product still in beta, the calculation tends to be: ship one platform really well, then expand.
Safari\'s share of the addressable market
Safari has about 19 percent of desktop browser market share globally as of 2026. That is meaningful but not dominant. The much larger Safari numbers (50+ percent in some markets) are on mobile via iOS, where browser extensions barely matter because most users live in apps. The desktop Safari user base that would actually install a Claude extension is small enough that Anthropic\'s priority calculus reasonably puts it behind other roadmap items.
That logic does not feel great to a Safari power user. It is, however, the logic.
The architectural friction nobody talks about
Safari\'s extension model is more restrictive than Chrome\'s in several specific ways that matter for AI-powered extensions like Claude in Chrome:
- Background scripts: Safari has stricter limits on background script execution than Chrome. Claude\'s extension needs persistent context and the ability to maintain state across page navigation, which is harder to implement reliably in Safari.
- Cross-origin restrictions: Safari\'s privacy model imposes stricter cross-origin policies than Chrome, which complicates the network requests that Claude in Chrome needs to make to Anthropic\'s API.
- Distribution friction: Safari App Extensions ship through the Mac App Store. Apple\'s review process is well-known for unpredictability when it comes to AI products, and the App Store has rejected previous AI browser extensions for vague policy reasons.
- Beta iteration speed: Anthropic is iterating on Claude in Chrome weekly. Shipping the same iteration speed through the Mac App Store review queue is structurally slow.
None of these are dealbreakers. They are real friction. For a product team trying to ship fast on a beta product, the friction adds up.
What the May 2026 Computer Use release changes
On May 13, 2026, Anthropic shipped a Claude Desktop release that turned Claude into something close to a Mac small-business automation tool. The release added Computer Use capabilities to the desktop app, letting Claude observe and interact with applications at the OS level.
Computer Use treats Safari specifically as a read-only application. Claude can see Safari (via screenshots), can navigate it indirectly (via the open -a Safari shell command), but cannot click, type, or scroll inside Safari. The tier is deliberate: Anthropic does not want Computer Use to be the path by which Safari is automated, because they have explicitly said an official Safari extension is not the right product surface.
The implicit position is: if you want Claude to act in your browser, use Chrome and the official extension. If you want Claude to read and observe Safari, you can do that through Computer Use. The split is product-defined, not just technical.
What this means for Mac users in practice
For most Mac users who use Safari as their primary browser, the practical answer in 2026 is one of three:
- Use Claude Desktop with Computer Use. Read and observe Safari through the OS-level workflow (
curlfor text,open -a Safarifor navigation, screenshots for visual context). No extension required. - Install AlliHat. A third-party Safari extension that puts Claude in a sidebar. Paid ($29/year), independent developer, not Anthropic. Useful if you want sidebar-style interaction.
- Use Chrome for AI tasks, Safari for everything else. Hybrid browser usage. Common pattern for power users who want the best of both ecosystems.
Option 1 is the path that costs nothing and works today. Option 3 is the path that gives you the full Claude in Chrome experience when you need it. Option 2 is the path that splits the difference.
Will Anthropic ever change its mind?
Probably, eventually. The pattern with companies in Anthropic\'s position is: ship the dominant platform first, then add others once the primary product is mature and the resource cost feels reasonable. OpenAI followed this pattern with ChatGPT on every platform. Google did it with Bard. Apple did it with iCloud on Windows.
The timing depends on three things: how big the Safari-only user complaint becomes, how much Anthropic\'s engineering capacity expands, and whether Apple changes the Safari extension model in a way that makes the build cheaper. The first is happening slowly. The second is true (Anthropic is hiring aggressively). The third is unpredictable.
Best guess: a Safari version of Claude\'s browser extension lands in 2027, conditional on Claude in Chrome reaching general availability first.
What to do today
If you have been holding off using Claude because you do not want to switch browsers, do not wait. The Computer Use workflow on Mac with Safari is functional, supported, and covers most read-and-observe research tasks. For action-heavy tasks where you need Claude to click and type in a browser, set up Chrome as your secondary browser for that purpose only. Most Mac power users we know run both, with Safari as primary and Chrome opened only for AI-driven workflows.
The waiting is not productive. The workflow exists. Use it.
At ScaleWise VA we built our internal AI-research playbook around this exact split. If you want help applying it to your own Shopify operations, book a free 30-minute call and we will show you the setup.
What this means if you run a Shopify store on a Mac
If you operate your Shopify business primarily through Safari (and many founders do, Safari has materially better battery life on MacBook Air, native Apple ecosystem integration, and stronger privacy defaults), the absence of an official Claude Safari extension does not mean you cannot use Claude in your daily operations. It means the workflow looks different.
For most Shopify operational tasks (auditing competitor storefronts, researching products, drafting customer emails, analyzing supplier data), the curl + open + screenshot pattern is functionally sufficient. We use it across store management retainers and customer support engagements without losing capability.
The one Shopify task where the absence of a Safari extension genuinely hurts is heavy Shopify admin interaction, bulk editing products through the admin UI, configuring app stacks, navigating multi-step settings flows. For these, you do need a browser-level AI assistant. Either install AlliHat ($29/year) inside Safari, or open Chrome as a secondary browser for AI-driven admin work specifically. Most Mac power users we work with run both browsers for this reason.
If you want help architecting an AI-augmented Shopify workflow on a Mac, our AI Workflows service covers exactly this kind of practical automation. Book a free call and we'll scope it for your specific store.