Detailed Analysis
A Reddit post in r/Anthropic captures growing frustration among paying Claude subscribers over apparent regressions in the GitHub connector feature, a tool that previously allowed users to sync repositories and manually select specific files or branches to include in a Claude session. According to the poster, a two-year Teams plan subscriber, this granular file-selection capability has disappeared, replaced by a workflow that forces Claude to perform a full repository analysis even when the user only needs a handful of specific files. This shift matters practically because it burns through token budgets unnecessarily, an especially painful outcome for teams on metered or capped plans who rely on efficient context management to keep costs predictable. The complaint also flags a more serious functional gap: an inability to access private repositories at all, which would undermine one of the core value propositions of a coding-focused AI assistant for professional developers who work primarily in private codebases.
Beyond the technical regression, the post highlights a recurring criticism of Anthropic's customer support infrastructure, particularly for paying business-tier customers. The user describes a billing dispute of roughly $150 that has gone unresolved for months, with automated chatbot responses claiming the issue has been "routed" to a human team, followed by long silences and eventual non-response even after 60-day windows. This pattern reflects a broader tension in the AI industry: companies scaling rapidly to meet explosive demand for coding assistants often under-invest in support infrastructure relative to the complexity and volume of enterprise and prosumer use cases. When a product is positioned as a professional developer tool, especially one integrated into GitHub workflows and paid at premium subscription tiers, users expect support responsiveness commensurate with traditional enterprise software vendors rather than consumer app support models.
The GitHub connector itself is a meaningful piece of Anthropic's developer ecosystem strategy, since Claude's coding capabilities (via Claude Code and integrated IDE tools) depend heavily on seamless repository access to be competitive with tools like GitHub Copilot, Cursor, and other AI coding assistants. Losing fine-grained branch and file selection functionality would represent a step backward at a moment when competitors are racing to improve repository-aware context handling, semantic search across codebases, and precise scoping of what gets fed into a model's context window. Efficient context selection is not a minor UX nicety, it directly affects cost, latency, and the relevance of a model's output, particularly for large monorepos where indiscriminate full-repo ingestion is both expensive and noisy.
More broadly, this complaint fits a pattern seen across the AI assistant space where product velocity, frequent feature changes, connector updates, and backend shifts, can outpace the support and communications infrastructure needed to manage user trust. As AI coding tools become embedded in daily professional workflows, disruptions to integrations like GitHub syncing carry outsized consequences, since developers depend on consistent, predictable behavior to integrate these tools into CI/CD and daily coding routines. Anthropic's ability to maintain trust with its professional and enterprise user base will likely hinge not just on model capability improvements, but on stabilizing connector reliability, restoring granular control features that power users depend on, and closing the gap between automated support triage and actual human resolution of account and billing issues.
Read original article →