Detailed Analysis
A Reddit post on r/Anthropic voices a common frustration among Claude power users: hitting attachment or image limits mid-conversation, forcing a workflow interruption where the user must migrate an entire project into Claude's Code/Projects environment just to continue working. The complaint, though brief and informally worded, touches on a recurring tension in how Anthropic structures access to Claude's capabilities—free and even paid tiers come with caps on file attachments, image uploads, and context usage within standard chat sessions, which can disrupt users who are deep in iterative, multi-file workflows.
This friction point matters because it exposes the gap between Claude's technical capability and its productized access limits. Claude models, particularly recent versions, support large context windows and multimodal inputs capable of handling substantial technical and visual material. However, Anthropic imposes usage caps—likely tied to compute costs, subscription tier, and rate-limiting infrastructure—that don't always align with how technical users actually work, especially those doing sustained coding or design sessions that involve repeated image or file references. The user's comment that attachment limits force a "transfer" into a separate coding-focused interface (likely referring to Claude Code or Projects) highlights that Anthropic's product surface is fragmented: chat, Projects, and Claude Code each have different constraints, and users bear the cognitive and workflow cost of navigating between them.
The post's framing—"they are subsidizing capabilities"—reflects a broader user theory that AI labs like Anthropic are deliberately throttling access to manage the enormous inference costs of running frontier models at scale. This is a widely held sentiment across AI communities: as models get more capable and expensive to serve, companies balance sustainable unit economics against user experience, often resulting in tiered caps that feel arbitrary or punitive to engaged users. Whether or not this is a deliberate "subsidization" strategy in Anthropic's case, the perception itself is telling of how users interpret friction in premium AI products—as a business constraint rather than a technical one.
The closing remark hoping "local llms fuck shit up" signals a broader undercurrent in AI discourse: growing interest in open-weight and locally-run models as a hedge against the limitations, costs, and control exerted by centralized API providers like Anthropic, OpenAI, and Google. As open models from Meta, Mistral, DeepSeek, and others close the capability gap with frontier closed models, users frustrated by rate limits and attachment caps increasingly see local inference as a form of leverage or protest against perceived artificial scarcity. This tension—between commercial AI providers optimizing for margin and cost control, and a user base pushing for unrestricted, self-hosted alternatives—is likely to intensify as both frontier model costs and open-model capabilities continue to evolve in parallel.
Read original article →