Stop a one-time comment becoming a permanent AI memory
Remove an overbroad Claude Code memory and keep only the context that should survive this task.
Suppose you tell Claude Code, “I'm near my model limit today, so keep review passes short.” If it saves “always minimize review passes,” tomorrow's work starts from the wrong rule. The fix has two parts: remove the mistaken memory in Claude Code, then decide whether anything from that conversation belongs in Jackdaw.
1. Find and remove the overbroad memory
In the affected Claude Code project, run /memory and open its auto-memory folder. Check MEMORY.md and the topic files for the saved rule. Also inspect any CLAUDE.md files that apply to this project. Claude Code's auto-memory is separate from CLAUDE.md; Anthropic explains how to inspect and edit both.
Remove or narrow the incorrect entry in Claude Code. Jackdaw's plugin can offer to import repository memory notes and turn Claude Code auto-memory off during setup. It does not erase an incorrect native memory entry for you. If a rule exists in both auto-memory and CLAUDE.md, fix both copies. Start a new Claude Code session and confirm it no longer treats the one-day limit as a standing preference. If overbroad entries keep appearing, /memory also lets you turn Claude Code auto-memory off. The coding-tool plugin offers the same choice during setup.
2. Decide what should survive
Use the scope of the original statement:
| What you said | Where it belongs |
|---|---|
| “Keep review passes short today; I'm near my limit.” | This task only. Leave it in the conversation or task notes. |
| “The Northwind figure is full; until design review, the planned changes are removals only.” | The Northwind project page, with the condition and review point. |
| “I generally prefer two review passes before asking for more.” | Your personal Jackdaw context, if that is truly an ongoing preference. |
Only put the second or third kind in Jackdaw. For a project-specific choice, open its Wiki page and write the condition and expiry or review point in your own words. For an ongoing personal preference, state it explicitly to Jackdaw or edit your Context page. Check Inbox suggestions and reject anything broader than you intended.
3. Test the boundary
With Jackdaw connected to Claude Code, start a new session and ask it to call get_context about the affected project. Check that the response includes the scoped choice and its condition. Then ask about an unrelated project. The one-day limit should not be treated as a standing Jackdaw preference there.
If Claude Code still applies the old rule, inspect its native memory again; an MCP connection does not override instructions or memories that Claude Code loads locally. Jackdaw helps you keep the facts and decisions you meant to carry forward, while the coding tool remains responsible for its own memory files and behavior.