@fingerskier/augment 0.2.1 → 0.3.0

package/docs/FEATURES.md

@@ -95,6 +95,29 @@ full index rebuild. Relative paths remain the durable identity.
   and DB row are removed and inbound frontmatter links in other memories are
   scrubbed). Delete is deliberately **not** exposed as an MCP tool.
 
+## Git auto-commit
+
+When the memory root is itself a git repository, the daemon auto-commits
+augment's own writes so the corpus carries its own version history — no manual
+snapshotting required.
+
+- **Enabled by default**; disable with `AUGMENT_GIT_AUTOCOMMIT=0` (also `false`,
+  `no`, `off`).
+- **Daemon-side and debounced.** Only augment's own mutations (upsert, delete,
+  link, unlink) schedule a commit; a burst of writes coalesces into one snapshot
+  commit. External/editor/Dropbox edits are *not* committed.
+- **Markdown only.** It stages `*.md` (`git add -A -- '*.md'`), so a nested state
+  dir or unrelated files are never swept in, and every memory mutation — including
+  deletes and link scrubs — is captured.
+- **Root-repo only.** It engages only when the memory root is the git worktree
+  root, never when it merely sits inside a larger project repo.
+- **Never pushes, always fails open.** Commits stay local; any git failure is
+  logged once and swallowed so a snapshot can never break a write. A fresh
+  `git init` with no configured identity still commits (a fallback
+  `Augment <augment@localhost>` identity is used only when none is set).
+- The check runs **once at daemon startup**, so enabling the flag or `git init`-ing
+  the memory root takes effect on the next daemon restart.
+
 ## Dashboard
 
 A daemon-served single-page web UI for browsing and editing memories as a graph:
@@ -327,6 +350,71 @@ groups a future `sleep` pass would distill into SPEC/ARCH records.
 - Mutates nothing. The write-back (`sleep_apply`) is deferred behind the
   Phase-2 dogfood go/no-go and does not exist.
 
+### `memory_insights`
+
+Aggregates a project's memory graph into dashboard insights.
+
+Inputs:
+
+```ts
+{ project_name?: string }
+```
+
+Behavior:
+
+- Resolves the project strictly (exact name, or a single unambiguous substring
+  match) — unlike `init_project` it never creates anything.
+- Returns a text summary (always) plus `structuredContent` with: totals
+  (memories/links/distinct tags/chars), counts by kind, links by type, top tags,
+  12 weekly activity buckets (created vs updated), most-connected memories,
+  orphan count, freshest memory, and the recall-quality tally when available.
+- In MCP Apps hosts (see below) the result renders as an interactive dashboard
+  snippet.
+
+### `memory_graph`
+
+Returns a project's memory graph for visualization.
+
+Inputs:
+
+```ts
+{ project_name?: string }
+```
+
+Behavior:
+
+- Text summary (node/link counts, top hubs) is always returned and points at
+  `augment dashboard` for the full experience.
+- The compact node/edge payload (capped at the 300 most recently updated
+  memories) is attached as `structuredContent` **only** when the client
+  negotiated the MCP Apps extension or `AUGMENT_MCP_UI_EMBED=1` is set — in a
+  text-only host it would only burn model context.
+
+## MCP Apps Dashboard Snippets (SEP-1865)
+
+The MCP server implements the [MCP Apps extension](https://github.com/modelcontextprotocol/ext-apps)
+(`io.modelcontextprotocol/ui`, spec version 2026-01-26):
+
+- Two UI templates are predeclared as resources with mime type
+  `text/html;profile=mcp-app`: `ui://augment/insights.html` and
+  `ui://augment/graph.html`. Both are fully self-contained HTML documents
+  (inline CSS/JS, Cytoscape inlined from `node_modules` at read time) so they
+  work offline under the extension's default CSP.
+- `memory_insights` / `memory_graph` reference their template via
+  `_meta.ui.resourceUri`; UI-capable hosts render the tool result in a sandboxed
+  iframe and stream data in over the spec's postMessage JSON-RPC
+  (`ui/initialize` → `ui/notifications/initialized` →
+  `ui/notifications/tool-result`). The snippets adapt to the host theme
+  (`hostContext.theme` + host CSS variables), auto-resize via
+  `ui/notifications/size-changed`, and the insights snippet can refresh itself
+  through the host-proxied `tools/call`.
+- Hosts without the extension ignore the metadata entirely and get the text
+  fallback — the tools stay useful in text-only hosts like CLIs.
+- Classic MCP-UI hosts (embedded-block renderers that never negotiate the
+  extension): set `AUGMENT_MCP_UI_EMBED=1` to append a self-contained
+  `type: "resource"` HTML block (data inlined, `mimeType: text/html`) to tool
+  results when — and only when — the client did not negotiate the extension.
+
 ## Configuration
 
 Resolution order:
@@ -340,6 +428,11 @@ Environment variables:
 - `AUGMENT_MEMORY_ROOT`
 - `AUGMENT_STATE_DIR`
 - `AUGMENT_DAEMON_PORT`
+- `AUGMENT_GIT_AUTOCOMMIT` — default on; set `0`/`false`/`no`/`off` to disable the
+  daemon's [git auto-commit](#git-auto-commit) of memory writes.
+- `AUGMENT_MCP_UI_EMBED` — set `1` to embed classic MCP-UI HTML blocks in
+  `memory_insights`/`memory_graph` results for hosts that render embedded
+  `ui://` resources but do not negotiate the MCP Apps extension.
 
 Defaults:
 

package/integrations/codex/SKILL.md

@@ -13,6 +13,14 @@ Use this skill when working in a repository with the Augment MCP server availabl
 2. Call `search` with the user's task summary.
 3. Read exact memories when search results identify likely governing context.
 
+## Memory Insights
+
+When the user asks for memory insights, stats, health, or an overview of what
+Augment knows, call `memory_insights` (and `memory_graph` when they want to see
+how memories connect). In hosts that support MCP Apps these render interactive
+dashboard snippets; elsewhere they return a text summary — either way, relay the
+findings rather than re-deriving them from raw memories.
+
 ## Before Code Changes
 
 1. Search for the file, component, command, error, or behavior being touched.

package/integrations/examples/claude-mcp-config.json

@@ -1,17 +1,17 @@
-{
-  "mcpServers": {
-    "augment": {
-      "command": "npm",
-      "args": [
-        "exec",
-        "--prefix",
-        "C:\\Users\\you\\.augment\\npm-exec",
-        "--",
-        "augment-mcp"
-      ],
-      "env": {
-        "AUGMENT_MEMORY_ROOT": "C:\\Users\\you\\Dropbox\\augment-memories"
-      }
-    }
-  }
-}
+{
+  "mcpServers": {
+    "augment": {
+      "command": "npm",
+      "args": [
+        "exec",
+        "--prefix",
+        "C:\\Users\\you\\.augment\\npm-exec",
+        "--",
+        "augment-mcp"
+      ],
+      "env": {
+        "AUGMENT_MEMORY_ROOT": "C:\\Users\\you\\Dropbox\\augment-memories"
+      }
+    }
+  }
+}

package/integrations/examples/codex-mcp-config.json

@@ -1,17 +1,17 @@
-{
-  "mcpServers": {
-    "augment": {
-      "command": "npm",
-      "args": [
-        "exec",
-        "--prefix",
-        "C:\\Users\\you\\.augment\\npm-exec",
-        "--",
-        "augment-mcp"
-      ],
-      "env": {
-        "AUGMENT_MEMORY_ROOT": "C:\\Users\\you\\Dropbox\\augment-memories"
-      }
-    }
-  }
-}
+{
+  "mcpServers": {
+    "augment": {
+      "command": "npm",
+      "args": [
+        "exec",
+        "--prefix",
+        "C:\\Users\\you\\.augment\\npm-exec",
+        "--",
+        "augment-mcp"
+      ],
+      "env": {
+        "AUGMENT_MEMORY_ROOT": "C:\\Users\\you\\Dropbox\\augment-memories"
+      }
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fingerskier/augment",
-  "version": "0.2.1",
+  "version": "0.3.0",
   "description": "Local RAG memory system for coding agents",
   "type": "module",
   "publishConfig": {
@@ -29,7 +29,7 @@
   "dependencies": {
     "@huggingface/transformers": "^3.8.0",
     "@libsql/client": "^0.15.15",
-    "@modelcontextprotocol/sdk": "^1.23.0",
+    "@modelcontextprotocol/sdk": "^1.29.0",
     "chokidar": "^4.0.3",
     "cytoscape": "^3.34.0",
     "gray-matter": "^4.0.3",