mirror of
https://github.com/rohitg00/agentmemory.git
synced 2026-09-14 20:16:33 +08:00
Rohit Ghumare
9c82d2aa7d
* chore(release): v0.9.29 with project-scope parity across surfaces Version trio + plugin manifests + supportedVersions + ExportData union bumped to 0.9.29; CHANGELOG entry covering everything since v0.9.28 with upgrade notes for the four visible behavior changes. Fixes the endpoint-count drift on main (130 registered routes vs docs saying 129 after #1132 landed in parallel with #1136). Project-scope parity: OpenCode plugin, Hermes plugin, Pi extension, and JSONL replay now resolve project the same way the hooks do (env override, git toplevel basename, cwd basename) instead of sending raw filesystem paths, closing #903 and #1135 and pre-empting the same bug in pi. The filesystem watcher accepts AGENTMEMORY_PROJECT_NAME with the old AGENTMEMORY_PROJECT kept as a deprecated alias, replay handles Windows-recorded paths, and OpenCode file enrichment matches the agent's lowercase tool names (the capitalized set never matched). Tests: opencode fallback expectations updated to basenames per the canonicalization, git-toplevel resolution covered with a fixture repo, new project-scope-parity suite for replay and fs-watcher. * fix(release): review findings, git-toplevel parity, doc counts - skills generator dedupes routes on method plus path, so the REST reference lists all 130 registered routes instead of hiding the second method on ten dual-method paths (header said 119) - fs-watcher trims AGENTMEMORY_PROJECT_NAME and the deprecated alias, treating whitespace as unset, and derives the git toplevel basename when watching a subdirectory - replay resolves the git toplevel basename when the recorded cwd still exists locally (memoized per cwd), keeping the basename fallback for historical or cross-platform paths; no env override here since a bulk import spans many projects - parity tests for replay git-root resolution, watcher git-root and trim behavior - stat-tests badge updated from 1428+ to 1550+ passing * fix(cli): refuse second-instance boot over a live daemon Closes the class behind issue 1140: agentmemory consolidate (or any unrecognized word) fell through the command table into the full server boot, registering a duplicate worker on the running engine; on iii 0.11.2 the second instance's shutdown tears down the daemon's HTTP trigger routing until a full engine restart. Unknown subcommands now error with the supported list, and main() probes livez on the resolved port and refuses to boot over a live daemon, so multi-instance setups on other ports are unaffected. Verified behaviorally against the built CLI: both paths refuse with exit 1. Also from review: the watcher stamps each event with its own root's project via a per-root map (an explicit config.project still overrides for every root), and replay only accepts a non-empty string cwd from parsed JSONL so malformed entries cannot reach the filesystem probe. * test(watcher): two-repository flush events scope to their own project * chore(release): bump packages/mcp, guard it, refresh CONTRIBUTING packages/mcp was still 0.9.28 after the release bump because nothing guarded it; a consistency test now pins it to package.json. CONTRIBUTING release list corrected to the files a bump actually touches (no tracked lockfile, the two extra plugin manifests, the export test derives from VERSION now), and the subsystems table gains src/cli, integrations/pi, and the generated-manifest note. * fix(export): refuse over-frame export instead of dropping the worker Closes the availability bug in issue 1142: GET /agentmemory/export assembles the full store and returns it through sdk.trigger, so a store whose serialized export passes the engine's 16 MiB WebSocket frame (tungstenite max_frame_size, not raisable under the 0.11.2 pin) dies on the worker->engine hop, drops the worker, and 404s every endpoint for ~1s. The session collections page on maxSessions/offset but ~18 others do not, so a large store hits this at any parameter combination. A shared frame-guard measures the serialized size before returning: mem::export returns a small oversized error instead of the giant object, and api::mesh-export returns 413 (same dead-end as #890). Either way the over-frame payload never crosses the boundary, so the daemon stays up and the failure is one clean request with a hint to narrow the range. Full pagination of the non-session collections is a follow-up. Layer 1 of the fix; verified with a synthetic oversized export returning the error object (tiny) rather than the payload. * ci: collapse to a single npm install to fix Node 24/26 CI The two-step install (npm install --package-lock-only then npm ci) failed only on the Node 24/26 matrix rows: their stricter npm rejects rolldown's optional platform bindings (@rolldown/binding-android-arm64) that a --package-lock-only pass does not fully enumerate. Lockfiles are gitignored, so npm ci re-validation buys no reproducibility here. A single lenient npm install resolves and installs in one pass. * fix(mesh): scope exported memories by project like actions api::mesh-export filtered actions by ?project but returned every project's memories. On a mesh instance federating one project to a peer, the peer pulled other projects' memories (cross-project leak), and those extras could push the payload past the 16 MiB transport frame into a 413 even when the requested project's own slice fit. Memories carry the same optional project field as actions, so filter both before the frame-size guard runs. Adds a regression test asserting a project-scoped export excludes other projects' memories and that an oversized memory in another project no longer 413s the scoped request. * chore(release): credit the Antigravity native hooks adapter in 0.9.29 notes * chore(release): sweep stale 0.9.28 refs for 0.9.29 Deploy Dockerfiles/compose/render pins, AGENTS.md stats header, opencode plugin manifest, website meta snapshot, test-count claims (1,428 -> 1,596) in README/AGENTS/stat SVGs, and the missing 0.9.29 CHANGELOG compare link. * chore(release): sync stat-tests badge to 1596+ and commit bridge exec bit * refactor: trim frame-guard comments and drop issue refs from code
@agentmemory/fs-watcher
Filesystem connector for agentmemory. Watches one or more directories and emits an observation to the running agentmemory server every time a file changes.
Part of the data-source-connectors effort tracked in issue #62.
Install
npm install -g @agentmemory/fs-watcher
Or run without installing:
npx @agentmemory/fs-watcher ~/work/my-repo
Usage
# CLI args win over env.
agentmemory-fs-watcher ~/work/my-repo ~/notes
# Or set env once in your shell.
export AGENTMEMORY_FS_WATCH_DIRS=~/work/my-repo,~/notes
export AGENTMEMORY_URL=http://localhost:3111
export AGENTMEMORY_SECRET=... # only if the server requires auth
agentmemory-fs-watcher
Every file change inside the watched roots becomes a post_tool_use observation whose data.changeKind is file_change or file_delete. The first 4 KB of each text file is included as data.content so retrieval can match by substring; larger files are truncated with data.truncated: true. Binary files are not read (set AGENTMEMORY_FS_WATCH_ALLOW_BINARY=1 to override).
Session id and project are required by the observe endpoint — set them via env, or the watcher generates a per-process fs-watcher-<ts>-<rand> session id and uses the first root's directory name as the project.
Requires Node.js >=20 LTS. Recursive fs.watch needs Node 19.1.0+ on Linux; Node 20 is the minimum supported LTS line.
Configuration
| Variable | Default | Meaning |
|---|---|---|
AGENTMEMORY_FS_WATCH_DIRS |
— | Comma-separated list of directories to watch |
AGENTMEMORY_FS_WATCH_IGNORE |
— | Comma-separated regex patterns to ignore (applied to relative paths) |
AGENTMEMORY_FS_WATCH_ALLOW_BINARY |
0 |
1 to include binary files in the preview read |
AGENTMEMORY_URL |
http://localhost:3111 |
agentmemory server URL |
AGENTMEMORY_SECRET |
— | Bearer token, required if the server has AGENTMEMORY_SECRET set |
AGENTMEMORY_PROJECT |
— | Optional project label attached to each observation |
AGENTMEMORY_SESSION_ID |
— | Optional session id to attribute observations to |
Defaults
Ignored out of the box: .git/, node_modules/, dist/, build/, .next/, .turbo/, coverage/, .DS_Store, *.log, *.lock. Extend with AGENTMEMORY_FS_WATCH_IGNORE.
Text extensions read for preview: common source, config, and docs (.ts/.js/.py/.go/.rs/.md/.yaml/...). Unknown extensions are recorded as a path-only observation without content.
Writes are debounced 500 ms per path so a stream of saves from your editor becomes a single observation.
Notes
- Uses Node's built-in
fs.watchwith{ recursive: true }. Works natively on macOS, Linux, and Windows 10+. No native deps. - If
fs.watcherrors on a specific root (permission, platform quirk), the watcher logs and continues on the others. - The process must keep running. Use a process manager (
launchd,systemd,pm2) to supervise it. - This connector is intentionally one-way: it writes observations and never reads the agentmemory store.