Detailed Analysis
A Reddit user on r/ClaudeAI has surfaced a nuanced and practically consequential question about how Anthropic's Claude Projects feature actually manages file loading and token consumption, exposing a gap between user-facing documentation and real-world behavior. The poster describes a sophisticated routing architecture built within a Claude Project — ten project files governed by trigger words in the project instructions — and reports that token burn is higher than expected. After consulting Anthropic's support documentation, the user concluded that below the 200K context window threshold, project files appear to load "flat," meaning all content enters context at conversation start regardless of whether it is needed for a given task. Caching, per their reading of the docs, reduces processing cost on repeated access but does not reduce the raw context footprint. The poster's central uncertainty is whether trigger words in project instructions can selectively influence *which* files load versus merely directing the model's attention within an already fully-loaded context — a distinction with significant token-efficiency implications.
The research context assembled around this question reveals an important terminological fault line that likely underlies much of the conflicting information the poster encountered. The tiered, conditional loading behavior described in the research — paths-based frontmatter, on-demand skill bodies, lazy `@file` pointer resolution — applies specifically to **Claude Code**, Anthropic's agentic coding environment, not to the Claude Projects feature available to Pro subscribers on claude.ai. Claude Code operates on a structured memory hierarchy rooted in `CLAUDE.md` files and `.claude/rules/` directories, where rules with `paths:` frontmatter load only when matching files are edited, offering genuine token savings of 50% or more on large repositories. This conditional architecture is meaningfully different from what the poster is working with, and conflating the two products — which both carry the "Claude" and "Projects" branding in various contexts — is almost certainly the source of the contradictory answers the user received, including from Claude itself.
For the poster's actual use case — Claude Projects on the Pro tier with uploaded project files and natural-language routing instructions — the flat-load hypothesis is almost certainly correct below the context window threshold. Anthropic's RAG activation appears to be a failsafe mechanism for knowledge bases that approach or exceed available context, not an efficiency feature that kicks in for smaller setups. This means the poster's ten project files are likely injected in full at conversation start, and the trigger words in the instructions are functioning as attentional cues to the model rather than as genuine conditional load signals. The practical implication is that the system, while functionally effective, does not achieve the token savings the user was hoping for through selective file loading — every conversation pays the full context cost of all ten files regardless of which workflow is invoked.
This exchange highlights a broader challenge in the current AI tooling landscape: the rapid proliferation of "Projects," "Memory," "Skills," and "Knowledge" features across Anthropic's product surface has created substantial terminological and conceptual overlap that even technically sophisticated users struggle to navigate. Claude Code's memory system represents a genuinely more mature and granular approach to context management, with explicit developer controls over loading tiers and token exposure. The consumer-facing Claude Projects feature, by contrast, appears to prioritize simplicity and reliability over fine-grained efficiency controls, which suits most users but creates friction for power users attempting to engineer token-optimal architectures. As Anthropic continues expanding both product lines, clearer documentation delineating these systems — and potentially backporting conditional loading primitives into the consumer Projects feature — would address a real and growing need among the increasingly sophisticated user base that has begun treating Claude Projects as a lightweight application deployment platform.
Read original article →