Cite as: Real Problem AI problem “Why does Claude Code re-inject the same skills and CLAUDE.md content instead of remembering it already loaded them?”. Opportunity score 7.2 out of 10 (severity 7, AI feasibility 8, market signal 7, competition gap 7). Category AI / Agents. Trend Agents. Source signal: anthropics/claude-code GitHub issue #29971, Ryan4n6, 2 Mar 2026.. Canonical URL: https://www.realproblem.ai/archive/why-does-claude-code-have-no-memory-of-what-context-it-already-loaded.
Why does Claude Code re-inject the same skills and CLAUDE.md content instead of remembering it already loaded them?
A community-maintained bug tracker documents 15 separate context-bloat issues stemming from missing dedup, cleanup, scoping, and visibility across skills, plugins, and MCP tool injection.
Who has it: Power users running many plugins, skills, and MCP servers inside Claude Code.
Evidence
The issue groups many context-bloat bugs as symptoms of missing context lifecycle management: no deduplication, cleanup, scoping, visibility or budget control.
Our summary of the public post linked below, not a quote. Nobody submitted it to Real Problem AI.
anthropics/claude-code GitHub issue #29971, Ryan4n6, 2 Mar 2026.Why it is archived
Trimmed to 100-cap (lowest opportunity_score)
Scoring breakdown
Existing players
- /context command · Underreports actual overhead per the report's own findings.
- Manual plugin/skill pruning · Users disable extensions by hand to claw back context.
What they are missing
A context-lifecycle manager that deduplicates repeated injections, caps system-overhead budget as a percentage of the window, and shows users exactly what's eating their context before it silently triggers compaction.
Stack hint
#ATB17 · Canonical URL: https://www.realproblem.ai/archive/why-does-claude-code-have-no-memory-of-what-context-it-already-loaded