untitled.md

Copilot memory script

Memory usage is opt-in while in public preview, so go to your Copilot settings to enable it.

Here we see a pull request making changes to an API and bumping the version accordingly. The Copilot code review agent is reviewing the changes for correctness, completeness, and quality. Let’s take a look at the session logs.

The code review agent noticed that the API version must remain synchronized across three parts of the codebase to prevent integration failures, and stored this learning as a memory.

A few days later a developer assigned the Copilot coding agent this issue which requires changes to the API.

The agent realizes that the API version must be bumped for its changes to take effect. The agent already knows three places it needs to bump the version because it's using the memory generated during a precious code review session. It reads the three cited code locations to verify the memory’s accuracy and then makes the needed code edits.

Copilot code review learned a key aspect of the codebase that the coding agent then applied to prevent subtle bugs and integration failures at runtime.

memory is in public preview, not private.

Also goes out today https://github.com/github/releases/issues/7742

if it's a talking head, when you say "a few days later" should it be you (a different developer) in a mustache?

can we hit this harder? maybe lead with the good news? "The agent already knows three places it needs to bump the version because it's using the memory generated during a precious code review session."

By using the memory generated during a previous code review session, the agent knows there are three places it needs to bump the version.