Skip to content

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

Rust

Merge main into fix/1657-capture-legacy-key-reuses-project

AkitaOnRailsb1b4b6585e48
diff --cc CHANGELOG.md
index 378a4a43,31110e25..13ec42b4
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -11,16 -11,34 +11,42 @@@ version in [`docs/changelog/`](docs/cha
## [Unreleased]
+ ### Changed
+
+ - `purge-project --confirm` without `--project`/`--project-id` now prints the
+ project it resolved from the current directory and the equivalent command
+ that names it, before the irreversible request. Naming the target will be
+ required in 4.0: from the wrong directory the derived name is the one project
+ nobody meant to delete, and a flag that spells it out is the only way to tell
+ the two cases apart (#1642).
+
### Fixed
+- A capture whose `.ai-memory.toml` names a promoted project's old name (its
+ v2 basename, now the project's `legacy_name`) no longer creates a second,
+ empty project under that name. The read path already resolved the old name
+ to the promoted project, so the twin made every later lookup of that name
+ fail as ambiguous until it was purged — and the next capture from the same
+ checkout created it again. The capture path now reuses the project the read
+ path resolves, and refuses an already-ambiguous name instead of adding a
+ third row (#1657).
+ - The cross-project profile no longer promotes an agent task brief into a
+ default for every project. Two more filters now apply: a prompt that wraps a
+ transcript or asks for a verbatim reply is the signature of a program
+ driving the agent through its SDK, and none of it is harvested; and a
+ sentence that switches off one of the agent's own capabilities ("Do not use
+ any tools.", "Never call browser_close") only becomes a preference when it
+ states cross-project scope. Two scripted one-shot prompts had reached
+ `min_projects` and shipped "do not use any tools" as a `tools` default with
+ confidence 0.95, which made agents ask for facts instead of looking them up
+ in the wiki they were already in (#1648).
+ - `purge-project --project ""`, and an empty `--project-id`/`--workspace`/
+ `--from`/`--to-workspace` on `move-project`, `purge-session` and
+ `rename-project`, are now refused before anything is sent. An empty flag
+ passed the "was the target named" check and then resolved as if it had been
+ omitted, so a script that passed an unset variable reached the project its
+ current directory resolved to — a real purge from an explicit-looking
+ invocation (#1642).
- `ai-memory workstream-search` now labels a historical tool call or tool
result as completed evidence, as the managed-workstream docs describe. Its
text output used the event's role, which every transcript adapter sets to