memgit 0.12.0__tar.gz → 0.14.0__tar.gz

{memgit-0.12.0 → memgit-0.14.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memgit
-Version: 0.12.0
+Version: 0.14.0
 Summary: Git for AI memory — version-controlled context persistence across Claude, GPT, Gemini, Cursor, Windsurf, and more
 License: MIT
 Project-URL: Homepage, https://memgit.dev
@@ -22,14 +22,14 @@ License-File: LICENSE
 Requires-Dist: click>=8.0
 Requires-Dist: rich>=13.0
 Requires-Dist: mcp<2,>=1.28.1
+Requires-Dist: pynacl>=1.5
+Requires-Dist: httpx>=0.27
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0; extra == "dev"
 Requires-Dist: pytest-anyio>=0.0.0; extra == "dev"
 Provides-Extra: tokens
 Requires-Dist: tiktoken>=0.7; extra == "tokens"
 Provides-Extra: cloud
-Requires-Dist: pynacl>=1.5; extra == "cloud"
-Requires-Dist: httpx>=0.27; extra == "cloud"
 Dynamic: license-file
 
 <p align="center">
@@ -160,7 +160,7 @@ pip install memgit
 ```
 (The Chocolatey package is live on community.chocolatey.org; newly pushed versions can take a few days to clear moderation — `pip install memgit` always has the latest.)
 
-**Any AI tool config (no Python needed — npx auto-installs on first run):**
+**Any AI tool config (needs Python 3.11+ on PATH; npx installs memgit into its own environment on first run and creates the store):**
 ```json
 { "mcpServers": { "memgit": { "command": "npx", "args": ["-y", "memgit-mcp"] } } }
 ```
@@ -216,15 +216,16 @@ memgit resume --json     # for tooling
 Wire it into Claude Code so memory becomes **automatic** — no tool call, no judgment required:
 
 ```bash
-memgit setup hooks       # installs all five hooks (~/.claude/settings.json)
+memgit setup hooks       # installs all six hooks (~/.claude/settings.json)
 ```
 
 | Hook | What it enforces |
 |---|---|
 | `SessionStart` | every session opens with the resume digest in context — status board, checkpoints, critical rules, memory index |
 | `UserPromptSubmit` | each prompt is BM25-matched against the store; relevant memories are injected, ending with a "+N more on '<topic>'" depth hint when more exists (silent when nothing clears the relevance bar; never repeats within a session) — `--no-recall` to skip |
+| `PreToolUse` | a Bash or file-write call that matches a memory's triggers is refused with the rule as the reason (priority-3 feedback and conventions) or gets the rule as context (the rest). memgit allow SLUG opens a short override window. Trigger cache only, `--no-gate` to skip |
 | `PostToolUse` | reading a file whose path matches a memory tag surfaces a one-line hint ("6 memories tagged 'x' relate to this path") — tagmap cache only, capped 3/session, `--no-ctx-recall` to skip |
-| `Stop` (guard) | a session that did real work but saved nothing gets ONE nudge to save durable facts before finishing — `--no-guard` to skip |
+| `Stop` (guard) | a governed call that went through without the gate, or a session that did real work but saved nothing, gets ONE block before finishing. `--no-guard` to skip |
 | `Stop` (sync) | markdown memories are checkpointed asynchronously at session end |
 
 Why hooks and not just good tool descriptions? We measured it: across 166 real sessions, hook-injected context was delivered in **100%** of them while voluntary memory-tool calls happened in **6%**. What a hook enforces happens.
@@ -284,6 +285,8 @@ Once registered via MCP, every AI tool gets 6 tools:
 
 The tool descriptions teach the AI **judgment** — "does this request depend on state you don't have in context?" — rather than keyword triggers. Measured cost of the whole tool surface: ~1,150 tokens once per session; a `resume_session` reply is ~335.
 
+**A save that arrives damaged is refused, not stored** (v0.13.0). A model sometimes closes a value with a tag named after the field (`</rule>`), and the host then delivers the next parameters inside that value: `why`, `when`, `tags` and `type_code` never arrive, and the memory is stored with defaults. On one machine that was 748 of 3,025 saves. `save_memory` now refuses any value carrying tool-call markup, names the field and the parameters it swallowed, and the model retries in the same turn. Markup quoted on purpose inside backticks is allowed. Every successful save echoes the length of each field it stored, which fields arrived empty, and which values came from a default. Damaged memories already in a store are never served back into context: the digest, the recall hook and read results show each field cut at the damage. `memgit doctor` counts them, and `memgit doctor --repair-markup` splits them back into their fields.
+
 ---
 
 ## Core operating guide (v0.5.0)
@@ -323,6 +326,29 @@ memgit pro deactivate         # remove the key from this machine
   exports keep working.
 - If this store is logged in to memgit cloud, `pro activate` also upgrades that account.
 
+### Sync between machines and with a team
+
+```bash
+memgit cloud signup --email you@example.com   # 14-day trial; keys are made on this machine
+memgit cloud team create myteam
+memgit cloud link myteam/memory               # creates the cloud repo on first link
+memgit cloud auto on                          # every save syncs in the background from now on
+```
+
+With autosync on, each save (including every `save_memory` your AI makes) starts one
+background pull-then-push and returns immediately, and each session start pulls what other
+machines saved. `memgit cloud auto status` shows the last run and why it would not run.
+
+On a machine that runs an agent but no interactive sessions (a Mac mini, a VM), log in and
+link once, then keep it current under systemd or launchd:
+
+```bash
+memgit cloud watch --interval 60                       # pull and push forever, one JSON line per run
+memgit cloud watch --export ~/agent/.hermes.md         # also write the digest for agents that read context files
+```
+
+Everything leaves the machine end-to-end encrypted; the server stores ciphertext only.
+
 ---
 
 ## Backups that actually happen
@@ -415,6 +441,8 @@ memgit doctor                     # hygiene + scope losses: split labels, quaran
 memgit doctor --audit             # every split and stranded label, the save landing rate, throughput
 memgit doctor --audit --json      # the same report as JSON
 memgit doctor --relabel map.json  # bulk re-project memories ({"slug": "Label" | ""}); one checkpoint
+memgit doctor --repair-markup     # dry run: memories whose fields swallowed other parameters on save
+memgit doctor --repair-markup --yes [--project LABEL]   # split them back into their fields; one checkpoint
 memgit lint                       # validate all memories (flags unknown provenance)
 memgit fsck                       # verify store integrity
 
@@ -441,7 +469,9 @@ memgit setup cline
 memgit setup continue
 memgit setup gemini-cli
 memgit setup hooks                # Claude Code hooks: resume at start, per-prompt recall,
-                                  # capture guard + auto-sync at stop (--no-recall / --no-guard)
+                                  # action gate on Bash and file writes, compliance and
+                                  # capture guard + auto-sync at stop (--no-recall / --no-guard / --no-gate)
+memgit doctor --rules             # critical rules next to same-topic lines in CLAUDE.md, AGENTS.md, ...
 
 # Pro (licence key)
 memgit pro activate <key>         # Polar-issued key; unlocks hosted E2E sync
@@ -506,6 +536,9 @@ memgit talks to nothing.
 | Cloud sync | `MEMGIT_CLOUD_API` | Overrides the memgit cloud API base URL. |
 |  | `MEMGIT_CLOUD_APP` | Overrides the memgit cloud web app base URL used in printed links. |
 |  | `MEMGIT_CLOUD_NO_CACHE` | Set to 1/true/yes to keep decrypted keys out of credentials.json; the passphrase is then re-prompted per command. |
+|  | `MEMGIT_NO_AUTOSYNC` | Set to 1/true/yes to stop saves and session starts from syncing to memgit cloud in the background, for this process only. |
+|  | `MEMGIT_AUTOSYNC_MAX_AGE` | Seconds after which a read (search, recall, an MCP lookup) starts a background fetch from memgit cloud (default 300). 0 turns read-triggered fetching off; saves and session starts still sync. |
+|  | `MEMGIT_AUTOSYNC_WAIT` | Seconds a session start waits for the fetch from memgit cloud before rendering the digest (default 3). 0 never waits. |
 | Tuning | `MEMGIT_LOCK_TIMEOUT` | Seconds a writer waits for the store lock before giving up (default 10). |
 |  | `MEMGIT_IDLE_EVICT_SECONDS` | Idle seconds before the MCP server drops its in-memory caches while staying connected (default 900). |
 |  | `MEMGIT_HOUSEKEEPING_INTERVAL` | Seconds between the MCP server's housekeeping passes. |

{memgit-0.12.0 → memgit-0.14.0}/README.md

@@ -126,7 +126,7 @@ pip install memgit
 ```
 (The Chocolatey package is live on community.chocolatey.org; newly pushed versions can take a few days to clear moderation — `pip install memgit` always has the latest.)
 
-**Any AI tool config (no Python needed — npx auto-installs on first run):**
+**Any AI tool config (needs Python 3.11+ on PATH; npx installs memgit into its own environment on first run and creates the store):**
 ```json
 { "mcpServers": { "memgit": { "command": "npx", "args": ["-y", "memgit-mcp"] } } }
 ```
@@ -182,15 +182,16 @@ memgit resume --json     # for tooling
 Wire it into Claude Code so memory becomes **automatic** — no tool call, no judgment required:
 
 ```bash
-memgit setup hooks       # installs all five hooks (~/.claude/settings.json)
+memgit setup hooks       # installs all six hooks (~/.claude/settings.json)
 ```
 
 | Hook | What it enforces |
 |---|---|
 | `SessionStart` | every session opens with the resume digest in context — status board, checkpoints, critical rules, memory index |
 | `UserPromptSubmit` | each prompt is BM25-matched against the store; relevant memories are injected, ending with a "+N more on '<topic>'" depth hint when more exists (silent when nothing clears the relevance bar; never repeats within a session) — `--no-recall` to skip |
+| `PreToolUse` | a Bash or file-write call that matches a memory's triggers is refused with the rule as the reason (priority-3 feedback and conventions) or gets the rule as context (the rest). memgit allow SLUG opens a short override window. Trigger cache only, `--no-gate` to skip |
 | `PostToolUse` | reading a file whose path matches a memory tag surfaces a one-line hint ("6 memories tagged 'x' relate to this path") — tagmap cache only, capped 3/session, `--no-ctx-recall` to skip |
-| `Stop` (guard) | a session that did real work but saved nothing gets ONE nudge to save durable facts before finishing — `--no-guard` to skip |
+| `Stop` (guard) | a governed call that went through without the gate, or a session that did real work but saved nothing, gets ONE block before finishing. `--no-guard` to skip |
 | `Stop` (sync) | markdown memories are checkpointed asynchronously at session end |
 
 Why hooks and not just good tool descriptions? We measured it: across 166 real sessions, hook-injected context was delivered in **100%** of them while voluntary memory-tool calls happened in **6%**. What a hook enforces happens.
@@ -250,6 +251,8 @@ Once registered via MCP, every AI tool gets 6 tools:
 
 The tool descriptions teach the AI **judgment** — "does this request depend on state you don't have in context?" — rather than keyword triggers. Measured cost of the whole tool surface: ~1,150 tokens once per session; a `resume_session` reply is ~335.
 
+**A save that arrives damaged is refused, not stored** (v0.13.0). A model sometimes closes a value with a tag named after the field (`</rule>`), and the host then delivers the next parameters inside that value: `why`, `when`, `tags` and `type_code` never arrive, and the memory is stored with defaults. On one machine that was 748 of 3,025 saves. `save_memory` now refuses any value carrying tool-call markup, names the field and the parameters it swallowed, and the model retries in the same turn. Markup quoted on purpose inside backticks is allowed. Every successful save echoes the length of each field it stored, which fields arrived empty, and which values came from a default. Damaged memories already in a store are never served back into context: the digest, the recall hook and read results show each field cut at the damage. `memgit doctor` counts them, and `memgit doctor --repair-markup` splits them back into their fields.
+
 ---
 
 ## Core operating guide (v0.5.0)
@@ -289,6 +292,29 @@ memgit pro deactivate         # remove the key from this machine
   exports keep working.
 - If this store is logged in to memgit cloud, `pro activate` also upgrades that account.
 
+### Sync between machines and with a team
+
+```bash
+memgit cloud signup --email you@example.com   # 14-day trial; keys are made on this machine
+memgit cloud team create myteam
+memgit cloud link myteam/memory               # creates the cloud repo on first link
+memgit cloud auto on                          # every save syncs in the background from now on
+```
+
+With autosync on, each save (including every `save_memory` your AI makes) starts one
+background pull-then-push and returns immediately, and each session start pulls what other
+machines saved. `memgit cloud auto status` shows the last run and why it would not run.
+
+On a machine that runs an agent but no interactive sessions (a Mac mini, a VM), log in and
+link once, then keep it current under systemd or launchd:
+
+```bash
+memgit cloud watch --interval 60                       # pull and push forever, one JSON line per run
+memgit cloud watch --export ~/agent/.hermes.md         # also write the digest for agents that read context files
+```
+
+Everything leaves the machine end-to-end encrypted; the server stores ciphertext only.
+
 ---
 
 ## Backups that actually happen
@@ -381,6 +407,8 @@ memgit doctor                     # hygiene + scope losses: split labels, quaran
 memgit doctor --audit             # every split and stranded label, the save landing rate, throughput
 memgit doctor --audit --json      # the same report as JSON
 memgit doctor --relabel map.json  # bulk re-project memories ({"slug": "Label" | ""}); one checkpoint
+memgit doctor --repair-markup     # dry run: memories whose fields swallowed other parameters on save
+memgit doctor --repair-markup --yes [--project LABEL]   # split them back into their fields; one checkpoint
 memgit lint                       # validate all memories (flags unknown provenance)
 memgit fsck                       # verify store integrity
 
@@ -407,7 +435,9 @@ memgit setup cline
 memgit setup continue
 memgit setup gemini-cli
 memgit setup hooks                # Claude Code hooks: resume at start, per-prompt recall,
-                                  # capture guard + auto-sync at stop (--no-recall / --no-guard)
+                                  # action gate on Bash and file writes, compliance and
+                                  # capture guard + auto-sync at stop (--no-recall / --no-guard / --no-gate)
+memgit doctor --rules             # critical rules next to same-topic lines in CLAUDE.md, AGENTS.md, ...
 
 # Pro (licence key)
 memgit pro activate <key>         # Polar-issued key; unlocks hosted E2E sync
@@ -472,6 +502,9 @@ memgit talks to nothing.
 | Cloud sync | `MEMGIT_CLOUD_API` | Overrides the memgit cloud API base URL. |
 |  | `MEMGIT_CLOUD_APP` | Overrides the memgit cloud web app base URL used in printed links. |
 |  | `MEMGIT_CLOUD_NO_CACHE` | Set to 1/true/yes to keep decrypted keys out of credentials.json; the passphrase is then re-prompted per command. |
+|  | `MEMGIT_NO_AUTOSYNC` | Set to 1/true/yes to stop saves and session starts from syncing to memgit cloud in the background, for this process only. |
+|  | `MEMGIT_AUTOSYNC_MAX_AGE` | Seconds after which a read (search, recall, an MCP lookup) starts a background fetch from memgit cloud (default 300). 0 turns read-triggered fetching off; saves and session starts still sync. |
+|  | `MEMGIT_AUTOSYNC_WAIT` | Seconds a session start waits for the fetch from memgit cloud before rendering the digest (default 3). 0 never waits. |
 | Tuning | `MEMGIT_LOCK_TIMEOUT` | Seconds a writer waits for the store lock before giving up (default 10). |
 |  | `MEMGIT_IDLE_EVICT_SECONDS` | Idle seconds before the MCP server drops its in-memory caches while staying connected (default 900). |
 |  | `MEMGIT_HOUSEKEEPING_INTERVAL` | Seconds between the MCP server's housekeeping passes. |

{memgit-0.12.0 → memgit-0.14.0}/memgit/__init__.py

@@ -1,3 +1,3 @@
 """memgit — git for AI memory."""
 
-__version__ = "0.12.0"
+__version__ = "0.14.0"