Continual-learning writes personal memory into tracked AGENTS.md in team repos

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

The marketplace continual-learning plugin writes personal memory into a team repo’s tracked AGENTS.md. This has been a recurring leak for months.

continual-learning: write to user-scoped memory file by default by yuranich · Pull Request #74 · cursor/plugins · GitHub already implements the safe default (write ~/.cursor/projects//AGENTS.local.md; repo writes opt-in and gitignore-gated). It has been open since 23 May 2026 with no maintainer review or merge. Meanwhile every plugin upgrade ships a new cache hash, wipes any local patch, and the next learning pass dirties AGENTS.md again. We have had to manually migrate bullets out of the team file and restore it multiple times; those Learned sections have also been committed by accident.

Please review/merge #74, or tell us what is blocking it. Leaving this PR idle keeps the plugin unsafe on any team repo that already owns AGENTS.md.

What happens today: after a learning pass the plugin appends “## Learned User Preferences” and “## Learned Workspace Facts” to the tracked team AGENTS.md. That shows up as a dirty git diff (and sometimes as a commit).

Steps to Reproduce

  1. Enable the marketplace continual-learning plugin in a git repo that already has a tracked AGENTS.md (team conventions, no Learned sections).
  2. Use Agent until the stop hook fires the continual-learning followup (or run the skill manually).
  3. Check git status / git diff on AGENTS.md.
  4. Optionally upgrade the plugin and run learning again: a new cache hash appears under ~/.cursor/plugins/cache/cursor-public/continual-learning/, and any local redirect patch is gone.

Expected Behavior

Write personal memory to ~/.cursor/projects//AGENTS.local.md by default. Only write the repo AGENTS.md if the user opts in (and preferably only if that path is gitignored). Do not append Learned sections to a tracked team AGENTS.md.

Operating System

MacOS

Version Information

Version: 3.19.13
VS Code Extension API: 1.128.0
Commit: dd066f332fcea7382764400fde902f61920648d0
Date: 2026-09-04T17:41:16.065Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

9

Hey @elissali, thanks for the report.

I’ll pass this along to the plugin maintainers, together with the community pull request you linked, so they can look at defaulting to a personal, untracked location and only touching a shared AGENTS.md when a user opts in!

I can’t promise a timeline on that. All that said, the plugin is open source so if the current behavior doesn’t fit how your team works, you’re welcome to fork it and change where it writes. You can even host that fork in a team marketplace for your team.

10

Hey Colin,

Thanks for the quick update and for passing this along to the maintainers! I completely understand about the timeline. We appreciate the suggestions and will look into the fork option if we need an immediate fix.