claude-code - 💡(How to fix) Fix [FEATURE] Need a RAG toggle in Projects [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46878Fetched 2026-04-12 13:30:40
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1unlabeled ×1

Fix Action

Fix / Workaround

Workaround today: Create compressed markdown "essentials" files that distill large reference docs into 1-2 pages, and only upload those. This works but requires manual maintenance every time a source document updates. A RAG toggle would eliminate this overhead entirely.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When I upload files to a Claude Project's knowledge base, if the total file size fits within the 200K context window, all files load in full into every conversation. This eats my working context — leaving less room for deep, multi-turn work.

The only way to trigger RAG (retrieval-on-demand) is to upload enough files to exceed the context window threshold. This forces power users to artificially bloat their knowledge base just to get selective retrieval behavior.

My workflow: I run 11 Projects across a consulting practice. Some need a small but focused reference library (5-10 pages of frameworks, vocabulary maps, pricing docs). I want those files searchable on demand, not loaded in full every time. Right now I have to choose between keeping files tiny (losing reference depth) or overstuffing to trigger RAG (wasting storage and degrading retrieval quality with filler).

Proposed Solution

Add a toggle in Project settings: "Use RAG retrieval" (on/off).

  • OFF (default): Current behavior. Files load in full into context.
  • ON: Files are indexed and retrieved on demand via the project knowledge search tool, regardless of total file size.

This is a one-toggle UX change. The RAG infrastructure already exists — it just needs a manual override instead of only activating at a size threshold.

Alternative Solutions

Workaround today: Create compressed markdown "essentials" files that distill large reference docs into 1-2 pages, and only upload those. This works but requires manual maintenance every time a source document updates. A RAG toggle would eliminate this overhead entirely.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implement a toggle in Project settings to enable "Use RAG retrieval" on or off, allowing users to choose between loading files in full into context or retrieving them on demand via the project knowledge search tool.

Guidance

  • Consider adding a configuration option to override the default behavior of loading files in full into context when the total file size is within the 200K context window threshold.
  • Evaluate the feasibility of integrating the proposed toggle with the existing RAG infrastructure to provide a seamless user experience.
  • Assess the potential impact of the toggle on storage usage and retrieval quality, and consider implementing measures to mitigate any negative effects.
  • Review the current workflow and use cases to ensure the proposed solution aligns with the needs of power users and does not introduce any unintended consequences.

Example

No code snippet is provided as the issue does not contain specific technical details or APIs.

Notes

The proposed solution relies on the existence of the RAG infrastructure, and its implementation may require modifications to the underlying system. The toggle should be designed to be user-friendly and intuitive, with clear documentation and guidance on its usage.

Recommendation

Apply workaround: Implement the proposed toggle in Project settings to enable "Use RAG retrieval" on or off, as it provides a flexible solution that caters to the needs of power users without requiring significant changes to the existing infrastructure.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING