Skip to content

feat(plugin/claude-code): mandate mem_context at session start to prevent blind sessions #138

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
franbaigorria wants to merge 1 commit into
base: main
Choose a base branch
from
+12 −0
Open

feat(plugin/claude-code): mandate mem_context at session start to prevent blind sessions #138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 12 additions & 0 deletions plugin/claude-code/skills/memory/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,18 @@ Format for `mem_save`:
- If unsure about the key, call `mem_suggest_topic_key` first, then reuse that key consistently
- If you already know the exact ID to fix, use `mem_update`

## SESSION START (mandatory)

Your FIRST action in every session — before responding to any user message — is to call `mem_context`.

Do this even if the first message seems unrelated to prior work (a pasted error, a build log, a greeting).
One call. Two seconds. Prevents a blind session.

If context shows prior work relevant to what the user is asking → use it immediately, don't re-explore what's already known.
If context is empty or irrelevant → proceed normally.

Do NOT skip this step. The cost of one call is negligible. The cost of a blind session is losing everything the previous session built.

## WHEN TO SEARCH MEMORY

When the user asks to recall something — any variation of "remember", "recall", "what did we do",
Expand Down