agent-memory-git 0.1.11__tar.gz → 0.1.13__tar.gz

{agent_memory_git-0.1.11 → agent_memory_git-0.1.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-memory-git
-Version: 0.1.11
+Version: 0.1.13
 Summary: Shared, git-backed memory for Claude Code and Codex.
 Keywords: claude-code,codex,memory,agents,git
 Author: Shichao Song

{agent_memory_git-0.1.11 → agent_memory_git-0.1.13}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "agent-memory-git"
-version = "0.1.11"
+version = "0.1.13"
 description = "Shared, git-backed memory for Claude Code and Codex."
 readme = "README.md"
 license = "MIT"

{agent_memory_git-0.1.11 → agent_memory_git-0.1.13}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "agent-memory-git"
-version = "0.1.11"
+version = "0.1.13"
 description = "Shared, git-backed memory for Claude Code and Codex."
 readme = "README.md"
 license = "MIT"

{agent_memory_git-0.1.11 → agent_memory_git-0.1.13}/src/agent_memory/PROTOCOL.md

@@ -26,6 +26,7 @@ Do not save:
 
 - progress or status updates, what you did this turn, or a recap of the conversation
 - the result of one run, live metrics, or anything else that should be looked up again rather than remembered
+- an instruction that holds only while something else is true, such as "leave the GPUs alone, another job is using them" or "don't push this week": that is state, not a preference; when you can't tell whether an instruction is standing or just for now, ask before saving it
 - code structure, paths you can rediscover, debugging recipes, git history, or anything already in the repository, its docs, CLAUDE.md or AGENTS.md
 - generic advice, or anything that matters only to the current conversation
 - secrets
@@ -39,8 +40,8 @@ Write one file per memory into this session's staging directory, with a short ke
 ```markdown
 ---
 name: kebab-case-slug
-type: feedback
-scope: global
+type: project
+scope: here
 description: One line (under 150 characters) saying what this memory is; it becomes the index entry
 ---
 The fact itself, in one or two sentences.
@@ -69,6 +70,8 @@ Keep the body under about 1,500 characters. A memory is a conclusion, not a log:
 - `global`: in every session. Use it for who the user is and for preferences not tied to one project.
 - `here`: only in this folder, its parent and child folders, and other checkouts of the same git remote. When the index marks the location as a throwaway folder (a scratch workspace or a Codex per-thread folder), `here` memories are filed under the project folder this session worked in most, so use `here` for project facts there too.
 
+A `project` or `reference` memory is `here` unless it holds in every project you could work in; a fact about one project, its repository or its tools stays `here`, however important it seems. Most `user` and `feedback` memories are `global`.
+
 Leave out ids, dates and provenance (session, host, folder, git remote). When your turn ends a hook adds them, moves the file into the repository and commits it.
 
 ## Changing existing memories