Detailed Analysis
A Reddit post surfaced complaining about an apparent forced GitHub integration blocking access to new chats in Claude's mobile app, with the user—a paying Pro subscriber—reporting they could not start a new conversation without connecting a third-party GitHub account they don't use. The post includes only a screenshot link and no additional technical detail, making it difficult to verify the scope, cause, or reproducibility of the issue from the available information alone. No official Anthropic statement, changelog entry, or corroborating reports are included in the research context, which limits the ability to confirm whether this reflects a genuine bug, a UI/UX rollout misstep, a permissions glitch tied to a specific account or feature flag, or a misunderstanding of an optional integration prompt that inadvertently blocked the primary chat flow.
This type of complaint matters because it touches on a recurring tension in consumer AI products: the push to integrate third-party developer tools and platforms (like GitHub, which Anthropic has increasingly woven into Claude's coding and agentic workflows) against the expectations of casual or non-technical paying users who simply want core functionality—like starting a chat—to remain frictionless. Anthropic has been aggressively expanding Claude's developer-oriented capabilities, including code execution, repository connections, and agentic coding features (e.g., Claude Code), reflecting a broader strategic bet that software engineering and technical workflows are a primary growth market. However, when integrations meant for power users or developers leak into or gate basic functionality for the general Pro subscriber base, it creates friction and erodes trust, especially among users who pay specifically for a general-purpose assistant rather than a coding tool.
The complaint also reflects a broader pattern across AI chat products where mobile apps often lag behind or diverge from web experiences in confusing ways, and where onboarding flows, permission prompts, or feature rollouts (particularly A/B tests) can behave unpredictably across different user segments. Enterprise and developer-focused features rolling out broadly—rather than being scoped narrowly to users who've opted into coding-related products—is a known failure mode for platforms trying to serve both casual consumers and technical professionals with a single app. If Anthropic did push a GitHub-linked onboarding or feature gate broadly, even inadvertently, it would be consistent with growing pains other AI companies have faced when trying to cross-sell agentic, tool-using capabilities to a subscriber base that may not want or need them.
Ultimately, without official confirmation from Anthropic or wider reporting, this remains an isolated user report rather than a confirmed platform-wide issue. It is illustrative of the kind of friction that can emerge as AI companies race to bundle increasingly powerful agentic and integration features (file access, code repositories, external tool connections) into consumer products, sometimes at the cost of the simple, low-friction chat experience that originally drove adoption. Such incidents typically prompt either a quick server-side fix, a clarifying statement from support channels, or silent rollback if enough users report similar blockages—but they also underscore the reputational risk of forcing unrequested third-party connections onto paying customers, particularly on mobile where users have less visibility into settings or workarounds compared to desktop or web interfaces.
Read original article →