Detailed Analysis
A Reddit post in r/ClaudeAI has struck a nerve among power users, articulating a frustration that has been building quietly as Anthropic's product surface has expanded rapidly: the sheer complexity of understanding what capabilities are available where within the Claude ecosystem. The original poster describes juggling Claude Desktop (Chat and Cowork), Claude Code CLI, Claude Code in Desktop, and the mobile app's Chat, Code, and Dispatch modes, plus Claude Design—and being unable to reliably predict which skills, plugins, connectors, or MCPs (Model Context Protocol integrations) are accessible in any given context. The post catalogs a tangled web of inconsistencies: skills installed via plugins live in a different settings menu than skills added directly; a skill installed in Claude Code CLI may or may not carry over to Claude Code Desktop depending on whether the session runs locally or in the cloud; local connectors work in some surfaces but not others; and MCP configuration requires digging through hidden system files while skills can simply be uploaded. The user's memorable framing—needing to open a "Schrödinger mystery box" every time they want to use a skill or MCP—captures a sentiment that clearly resonated, given the thread's traction.
This complaint matters because it exposes a structural tension in Anthropic's product strategy. Over the past year, Anthropic has aggressively diversified Claude's surfaces and extensibility mechanisms: the Model Context Protocol was introduced as an open standard for connecting Claude to external tools and data sources, "Skills" emerged as a way to package reusable capabilities and instructions, "Plugins" arrived as a bundling mechanism for skills and connectors, and Claude Code has spun off into multiple runtime environments (CLI, desktop-integrated, and cloud/sandboxed sessions). Each of these was likely introduced to solve a specific problem—portability, tool access, workflow automation—but layered together without a unified mental model, they've created what the poster describes as a combinatorial explosion of edge cases. Whether a given skill or connector is available depends on an opaque interplay of which client you're using, whether the session is local or cloud-hosted, whether a container has access to your home directory, and which settings panel happens to govern that particular integration type. For technical users trying to build reliable workflows, this unpredictability undermines trust in the platform and adds cognitive overhead that offsets the productivity gains these features are meant to deliver.
The episode reflects a broader pattern in the AI industry: as agentic coding tools and assistant platforms race to add extensibility—plugins, tool-calling standards, memory systems, sandboxed execution environments—the underlying architecture often outpaces coherent user-facing design. Anthropic is not alone in this; OpenAI, Google, and others have faced similar criticism as they bolt on custom GPTs, extensions, and connector ecosystems to their own assistants. The friction described here is characteristic of a "platform sprawl" problem, where a company iterates quickly across multiple product lines (consumer chat, developer CLI tools, enterprise cloud sessions) without maintaining a single source of truth for configuration and capability. For a product like Claude Code, which is increasingly positioned as a serious tool for professional developers automating real workflows, this kind of fragmentation is a meaningful liability—developers need deterministic, inspectable systems, not ones where behavior appears to exist in "superposition."
More broadly, the thread signals a maturation point for Anthropic's product ecosystem: the company has clearly prioritized rapid feature velocity and openness (MCP as an open protocol, skills as portable packages) over unified interface design. As Claude's user base grows beyond early AI enthusiasts into mainstream developers and enterprise teams, pressure will likely mount for Anthropic to consolidate settings, standardize how capabilities propagate across local and cloud environments, and provide clearer visibility into what's active in any given session. How the company responds—whether through a unified capabilities dashboard, clearer documentation, or architectural simplification—will be a useful indicator of whether Anthropic can balance its fast-moving experimentation with the reliability that professional and enterprise adoption increasingly demands.
Read original article →