Problem
- Incorrect guidance - Agents receive irrelevant facts about Tizen workloads, Apple TPVs, Blazor TypeScript builds, etc.
- Context pollution - Valuable context window space is wasted on memories from other projects
- Confusion - Agents must spend time verifying whether memories are relevant or not
Example Memorie
- Blazor TypeScript build: "In .NET 10, TypeScript MSBuild + Razor class library multi-TFM build causes..." (from SkiaSharp.Views project)
- Apple TPV resolution: "With .NET 10 SDK, bare net9.0-ios resolves to TPV 26.0..." (from SkiaSharp builds)
- Tizen workload TPVs: "Samsung Tizen SDK 10.0.123 supports TPVs 8.0-11.0..." l
- MAUI Tizen support: "MAUI 10.0 dropped Tizen support..." (from SkiaSharp NativeAssets)
Expected Behavior
Repository memories should be:
- Scoped to the current repository -
- User-specific - Memories from user's other projects should not leak into unrelated repos
- Verified - The system should validate that citations actually exist in the current repo before showing memories
Current Workaround
Agents must:
- Carefully read citations to verify if memories are relevant
- Manually filter out cross-contaminated memories
- Store corrected memories to override bad ones
Suggested Fix
- Add repository scoping to memory storage (store
repo_owner/repo_name with each memory)
- Filter memories by current repository when loading session context
Environment
- GitHub Copilot CLI: 0.0.408
- Contaminated with memories from: mono/SkiaSharp (or similar)
Problem
Example Memorie
Expected Behavior
Repository memories should be:
Current Workaround
Agents must:
Suggested Fix
repo_owner/repo_namewith each memory)Environment