Detailed Analysis
A user report on the r/ClaudeAI subreddit highlights a functional complaint rather than a formal news development: since adopting Anthropic's "cowork" feature (a collaborative or multi-context work mode within Claude), the poster describes the standard chat interface becoming largely unusable. Fresh conversations reportedly time out or trigger errors demanding that tens of thousands of tokens be reduced before a query can even be submitted, regardless of which model is selected. The user also notes an inability to use Claude at all on mobile, and asks whether some memory-related feature needs to be disabled to restore normal function. No official Anthropic response or fix is included in the post, and no additional corroborating reports or context were found, suggesting this may be an isolated or narrowly reproduced issue rather than a widespread outage.
The specifics point to a likely culprit: context window bloat carried over from persistent memory or session-linking features. If "cowork" maintains a shared or continuously accumulating context across sessions—akin to how some AI products implement long-term memory or project-based context retention—then even a "fresh chat" could inherit a large hidden token payload from prior sessions, explaining why brand-new conversations are immediately flagged for exceeding practical token limits. This would also account for the mobile app being non-functional, since mobile clients typically have less tolerance for oversized context payloads and fewer diagnostic controls to let users trim or reset accumulated state manually.
This complaint sits within a broader pattern of friction that emerges whenever AI companies layer new "agentic" or collaborative capabilities—like Claude's Code interpreter, computer-use tools, or now cowork-style multi-session features—on top of core chat products. These features are generally designed to give Claude more persistent context so it can reason across longer tasks, coordinate multi-step work, or remember prior instructions. But persistent context is a double-edged sword: it improves continuity for legitimate use cases while risking silent, compounding token overhead that degrades the baseline chat experience for users who simply want lightweight, stateless conversations. Anthropic, like OpenAI and Google with their own memory and agent features, has had to navigate this tension between "smarter, more contextual" assistants and predictable, low-latency, low-cost interactions.
More broadly, this kind of user-reported friction reflects a recurring theme in the current wave of AI product development: feature layering often outpaces the maturity of user controls. As vendors race to add agentic capabilities, multi-app orchestration, and long-term memory to differentiate their products, granular settings to manage, inspect, or purge that added context frequently lag behind. Users are left without clear mechanisms to diagnose why a "fresh" session is behaving as if heavily loaded, and support surfaces like Reddit become de facto channels for troubleshooting rather than official documentation or in-app diagnostics. For Anthropic specifically, resolving this kind of complaint—likely through clearer memory/context toggles, per-session reset controls, or better mobile parity—will be important for maintaining trust as Claude expands from a single-turn chat assistant into a more persistent, agentic, cross-device system.
Read original article →