Skip to content

Repository memories from different projects appearing in sessions (cross-repo contamination) #1439

@PureWeen

Description

@PureWeen

Problem

  1. Incorrect guidance - Agents receive irrelevant facts about Tizen workloads, Apple TPVs, Blazor TypeScript builds, etc.
  2. Context pollution - Valuable context window space is wasted on memories from other projects
  3. 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:

  1. Scoped to the current repository -
  2. User-specific - Memories from user's other projects should not leak into unrelated repos
  3. Verified - The system should validate that citations actually exist in the current repo before showing memories

Current Workaround

Agents must:

  1. Carefully read citations to verify if memories are relevant
  2. Manually filter out cross-contaminated memories
  3. 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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions