Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

Merge remote-tracking branch 'origin/release/2.7' into feat/1241-ingest-drop-list

AkitaOnRails80f3033a5424
diff --cc CHANGELOG.md
index c503f12a,bb98054d..2fd7f91b
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -307,13 -320,23 +320,30 @@@ and this project adheres to [Semantic V
- `ai-memory status` and `ai-memory doctor` now show the server's auth
posture, and for an unauthenticated loopback server print
`auth: none (loopback)` with the fix, `ai-memory auth enable`.
+- Added a server-side drop list for tool events: `[ingest]
+ drop_tool_use_id_prefixes` and `drop_tool_names` (both empty by default, at
+ most 64 entries of 128 characters). A PreToolUse or PostToolUse event whose
+ tool-use id starts with a listed prefix, or whose tool name matches exactly,
+ is answered with 202 and counted as a policy drop in `/hook` and
+ `/hook/batch`, before it is sanitized, rate-limited or stored. The lists
+ apply to every project on the server. (#1241)
+ - Added `--project-id` to `purge-project`, `rename-project` and
+ `move-project` (and `project_id` to their admin endpoints), as an
+ alternative to the project name. A legacy twin row whose name collides with
+ another project's `legacy_name` (the empty leftover an older migration
+ leaves behind) was refused as ambiguous by name, so it could not be purged
+ or renamed. The id is looked up inside the named workspace: sending both or
+ neither is a 400, a malformed UUID is a 400, and an id that names no project
+ in that workspace is a 404. `list-projects` now prints each project's id so
+ an operator can copy it, and `GET /api/v1/projects` rows carry
+ `workspace_id` and `project_id` (hidden with the row for a restricted
+ project). (#1208, #1226)
+ - Added `ai-memory project init`, which creates a `.ai-memory.toml` marker at
+ the current worktree root (or the current directory outside Git) after
+ asking for `workspace` and `project`. The defaults are the scope the CLI and
+ hooks already resolve for the checkout, so accepting them keeps the memory
+ where it is. It writes only those two keys, needs an interactive terminal,
+ and never overwrites an existing marker. (#1227)
### Changed
- Changed scoped `/api/v1/search` (a single `workspace` + `project`, or