Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #1247: feat(web): page folders and namespaces by recency
AkitaOnRailse7d7a03357e0
diff --cc CHANGELOG.mdindex 82fbe76f,7a41a2ab..301de0f0--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -354,48 -348,13 +354,53 @@@ and [0.x](docs/changelog/0.x.md)hooks already resolve for the checkout, so accepting them keeps the memorywhere it is. It writes only those two keys, needs an interactive terminal,and never overwrites an existing marker. (#1227)+- Added first-class Factory Droid CLI support. `install-mcp --client droid`+ (alias `factory-droid`) merges an HTTP entry into `~/.factory/mcp.json`,+ with the URL written literally and a bearer referenced as+ `Bearer ${AI_MEMORY_AUTH_TOKEN}`: Droid expands variables in headers but+ never in the URL.+ `install-hooks --agent droid` merges native+ `ai-memory hook --event … --agent droid` commands for seven events into+ `~/.factory/hooks.json`, keeps your own entries, changes nothing on a+ re-run, and refuses to create that file while `~/.factory/settings.json`+ holds hooks, which Droid would then stop reading. Sessions are recorded as+ agent `droid` (migration V78). The `SessionStart` hook delivers the pending+ handoff, and Droid's own `SessionEnd` closes the session. Droid's `Read`,+ `Create`, `Edit`, `ApplyPatch`, `LS`, `Grep`, `Glob` and `Execute` tools+ map to the file, search and shell families, so `[capture] ignore_paths`+ applies to them: verified against the Droid 0.240.0 tool schemas; no+ tool-call id in Droid payloads. `setup-agent --agent droid` prints the+ hook config and `uninstall` removes both entries. (#1240)+- Added an optional TypeScript client SDK in `companions/ai-memory-ts` for+ programs that are not coding-agent harnesses: custom agents, bots, editor+ and app extensions, scripts and CI jobs. `AiMemoryClient` wraps the page,+ query, status, recent, handoff, message, briefing, explore,+ session-observation and feedback tools, the read-only `/api/v1` routes (with+ cursor paging and `ETag` revalidation) and `GET /identity`, with typed+ results, a typed error taxonomy and scope checks before any request.+ `pages.update` reads a page, applies a change and writes it back guarded by+ `expectedPageId`, keeping the page's metadata. A separate+ `ai-memory-ts/admin` entry point covers checkpoints, page restore and+ session or project purges, which default to a dry run and need both+ `dryRun: false` and `confirm: true` to delete. The SDK has no runtime+ dependencies, needs Node 22 and a 3.0.0 server, and is built from a checkout+ for now; it is not published to npm and is never part of the server's+ tarballs, Docker image, Homebrew, AUR, RPM or Nix packages, which+ `scripts/check-native-packaging.sh` now enforces. CI runs it against the+ server built from the same commit, including a schema drift test that fails+ when an MCP tool changes without an SDK update. See+ `companions/ai-memory-ts/README.md` and `docs/design-client-sdk.md`. (#1165)### Changed+- Documented the 2.x to 3.0 upgrade in `docs/upgrading-to-3.0.md`: what+ changes, what replaces the removed token commands, the backup, upgrade and+ check steps, and how to roll back by restoring the backup with the 2.x+ binary. README, `docs/install.md` and `docs/MIGRATION-2.0.md` link to it.+ - Changed the web UI's project sidebar to link each folder to its namespace+ listing with a page count, and to show only its five most recently updated+ pages with a "View all N" link. The namespace listing now sorts by recent+ update or by title and shows 25 pages at a time with previous and next links+ (`?sort=title&page=2`). (#1247)- Changed scoped `/api/v1/search` (a single `workspace` + `project`, or`scopes`) to rank with the same hybrid ranker as `memory_query` instead ofFTS5 alone, so it returns the same order as `memory_query`, and `rank` is