Skip to content

Add memory instructions for agent improvements across 🤖 users #6203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Trenly wants to merge 3 commits into
base: master
Choose a base branch
from
+30 −0
Open

Add memory instructions for agent improvements across 🤖 users #6203

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
24351ec
Add custom instruction for handling memory updates
Trenly May 3, 2026
4df7f24
Ensure file is loaded as instructions file
Trenly May 3, 2026
2ca13ae
Adjust for new file name
Trenly May 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions .github/instructions/copilot-memory.instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
applyTo: "**"
---

# Copilot Memory

Preferences and conventions learned from working in this repository. Any conventions that are not explicitly mentioned here should be inferred from the codebase.

## How to Handle Corrections

When a user corrects you on terminology, naming conventions, workflow preferences, or any other practice that applies repository-wide (not just to the current task), follow these steps:

1. **Recognize the correction.** A correction has occurred when the user tells you that something you said, named, or did is wrong or should be done differently — especially if it involves consistent patterns such as naming conventions, terminology, architectural practices, or tool usage.

2. **Assess the scope.** Ask yourself: *Would other contributors to this repository benefit from knowing this? Would a future agent session make the same mistake without this guidance?* If yes, it is a candidate for shared repository memory (this file). If the correction is personal to this user (e.g., a workflow preference or output style), it is a candidate for user memory instead.

3. **Ask the user before storing.** Do not silently write to either location. Instead, ask:

> "Should I remember this correction for the future? If so, should I add it to the **repository memory** (`copilot-memory.md`) so all contributors' agents benefit, or as a **user memory** (via the memory skill) that applies only to your sessions?"

Offer both options clearly and let the user decide.

4. **Act on the answer.**
- If **repository memory**: add a concise, unambiguous entry under the appropriate section of this file (`copilot-memory.instructions.md`) and commit it.
Comment thread
Trenly marked this conversation as resolved.
Copy link
Copy Markdown
Member

@JohnMcPMS JohnMcPMS May 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For repository memories, we should also consider if they should be scoped to prevent the root instructions from becoming too large. For instance, your addition of the SQL builder should be scoped to the locations that use it (shared, repository, tests).

- If **user memory**: call the `store_memory` tool with a clear `fact`, a `reason` explaining when it applies, and a `citations` reference to this conversation or the relevant file.
- If **neither**: acknowledge and move on without storing.

## Terminology

- Use **Packaged** and **Unpackaged** (not "Package context" / "Non-package context") when referring to the two WinGet execution contexts.