Detailed Analysis
A Claude Pro user running a 2017 MacBook Pro on macOS Ventura reports that the top navigation tabs — specifically Coworker, Chat, and Code — are absent from the Claude desktop application despite a confirmed active subscription, repeated clean reinstalls, and a fully updated operating system. The user has exhausted the most common self-service remediation steps, including downloading fresh copies from the official site, restarting the machine between each install, and verifying account consistency across desktop, web, and mobile platforms. Community research turned up conflicting information, with some sources pointing to Intel Mac incompatibility as the root cause, while others described workarounds that were either Windows-specific or inconclusive for macOS environments.
The core technical issue, as documented across multiple GitHub issues on the anthropics/claude-code repository, stems from a combination of known bugs that cause the Cowork tab to disappear or fail to initialize. Reported triggers include auto-update failures in versions such as v1.1.7714 and v2.1.11, where the Cowork runtime is simply absent from the deployed app bundle, as well as authentication-layer problems involving service workers and connection resets. There is also a prerequisite requirement — Virtual Machine Platform enablement — that the desktop app checks during Cowork setup and which can silently block tab rendering if not satisfied, even when all subscription and connectivity conditions are otherwise met. These conditions compound on older Intel-based hardware, where certain virtualization and runtime dependencies behave differently than on Apple Silicon machines.
The compatibility dimension is significant and underreported in user-facing documentation. While Anthropic has not issued an explicit statement declaring Intel Mac support deprecated, the practical experience of users on pre-2020 hardware increasingly diverges from the intended feature set. The Cowork feature — Anthropic's agentic, computer-use-enabled workspace within the desktop app — relies on sandboxed execution environments and virtual machine capabilities that are more reliably instantiated on Apple Silicon hardware with its unified memory architecture. A 2017 MacBook Pro, while capable of running macOS Ventura and the Claude app itself, may fall short of the underlying runtime requirements that Cowork depends upon, explaining why even flawless reinstall procedures yield no resolution.
This report situates itself within a broader pattern of friction users experience at the intersection of rapidly evolving AI feature rollouts and aging consumer hardware. Anthropic has been expanding the Claude desktop app's capabilities at a pace that prioritizes modern hardware assumptions, particularly as agentic and computer-use features demand more from local system resources and virtualization layers. The gap between what users expect based on a paid subscription and what the software silently requires in terms of hardware generation represents a communication failure as much as a technical one — affected users are discovering hard limits through community forums rather than through clear in-app messaging or documentation. This is a recurring dynamic across the AI application space, where feature velocity outpaces compatibility transparency.
For the affected user and others in similar situations, the most actionable paths forward are limited but defined. Checking for a Virtual Machine Platform availability prompt within the app's Cowork setup flow may surface whether the hardware prerequisite is the specific blocker. If the tab remains absent after that check and a verified reinstall, filing a detailed bug report on the anthropics/claude-code GitHub repository — including macOS version, app version, and any Feedback ID surfaced in app logs — contributes to the documented issue cluster, with duplicates already logged under issue numbers such as #18474. Until the hardware upgrade the user is planning materializes, the Cowork feature may remain inaccessible, as no Mac-specific workaround for Intel-generation compatibility has been reliably confirmed in the existing community record.
Read original article →