Detailed Analysis
A user on the r/Anthropic subreddit has documented a reproducible and technically specific failure in Claude's project file ingestion pipeline, reporting that CSV and XLSX files added to Claude Projects appear to upload successfully but deliver empty content to the model's context window. The failure began approximately two days before the post date of April 30, 2026, and represents a regression from months of stable operation. The user provided precise diagnostic detail: when a CSV is ingested via the normal project pipeline, the resulting document block contains only the filename and encoding metadata — the content body is entirely absent — with no error message surfaced to the user or to the model. This silent failure means the UI reports the file as successfully added, the percentage-used indicator does not increment, and Claude has no content to work with despite believing ingestion succeeded. A secondary failure mode was also documented for Google Drive-connected files, which return a quota error from the Sheets API (`sheets.googleapis.com`) even when quota exhaustion appears unlikely.
The technical nature of the failure points to a server-side regression in Anthropic's document ingestion pipeline rather than a client-side or user-error issue. The fact that PDFs continue to work correctly while CSV and XLSX files fail suggests the breakage is isolated to the processing pathway for tabular file formats, which likely follows a different extraction and encoding route than binary document formats like PDF. The user's observation that files added directly to individual chats still function — as opposed to project-level uploads — further narrows the failure to the persistent project storage and retrieval layer. The Google Sheets quota error introduces a separate but potentially related dimension, suggesting that the integration layer between Claude Projects and Google Drive may also be experiencing degraded or rate-limited service. Neither failure produces a user-visible error, which substantially increases the severity from a product reliability standpoint, as users cannot distinguish a successful ingestion from a failed one.
This incident carries meaningful implications for users who depend on Claude Projects for professional workflows involving structured data. The affected user described a financial planning and research use case requiring daily file updates across multiple spreadsheets — precisely the kind of high-frequency, data-intensive workflow that Projects was designed to accommodate. The inability to use XLSX or CSV files at the project level, combined with the workaround of re-uploading files to each individual chat, undermines the core value proposition of Projects as a persistent, shared-context workspace. The research context notes that Claude supports CSV and Excel as documented formats, and that enabling the "analysis tool" under experimental settings is sometimes required — but that setting is reported as already enabled by the user, and the silent content-blank failure pattern described here is distinct from a capability or configuration issue.
Broader trends in AI product development make this class of failure particularly worth noting. As frontier AI systems move beyond pure conversational use toward agentic and long-context workflows — where users maintain persistent project contexts, connect external data sources, and rely on the model to reason over large structured datasets — the reliability of the data ingestion layer becomes as critical as the model's reasoning capability itself. A model that silently receives empty documents and proceeds as if content were present risks producing confidently wrong outputs, which is especially dangerous in financial or analytical contexts. Anthropic has been actively positioning Claude Projects and tool integrations as core enterprise features, making silent ingestion regressions a reputational as well as functional concern. The two-day support ticket response gap noted by the user also highlights the growing support load challenges that accompany rapid user adoption of these more complex, integration-heavy product surfaces.
Read original article →