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/main' into merge-438

AkitaOnRails2ae4ea2459a5
diff --cc CHANGELOG.md
index a89a0fab,ac7b35e6..fac793f1
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -7,26 -7,55 +7,65 @@@ and this project adheres to [Semantic V
## [Unreleased]
+### Added
+- `ai-memory status` now reports local hook-spool health: pending event
+ count, age of the oldest queued event, and total failed-delivery attempts.
+ This makes "memory capture is delayed, not broken" visible to an operator
+ without digging through logs: a non-empty spool or an aging oldest event
+ means hook events are queued locally instead of reaching the server. The
+ spool is client-side, so the section reflects the local data-dir even when
+ the server is remote. The JSON form gains a matching `spool` object
+ (`pending`, `oldest_age_ms`, `retries_total`). (#428)
- - New `strip_root_combinators` config flag (env `AI_MEMORY_STRIP_ROOT_COMBINATORS`,
- or `strip_root_combinators = true` in config.toml) strips root-level
- `anyOf`/`oneOf`/`allOf` from MCP tool input schemas on every `tools/list`.
- Generic MCP clients such as OpenCode and Cursor never send the `?flavor=`
- marker, yet forward schemas verbatim to strict upstreams (Moonshot, Bedrock)
- that reject root combinators with a 400 — this gives operators behind such an
- upstream a mode-independent opt-in. Runtime "exactly one of" validation is
- unchanged ([#412]). The key is documented in the generated
- `config.default.toml` so it is discoverable without reading the source.
+
- ### Fixed
+ ## [1.29.0] - 2026-08-19
+
+ ### Fixed
+ - Corrected the Pi/OMP extension filenames in `README.md`, `docs/install.md`,
+ and `docs/mcp-install.md`, which still described the pre-rename
+ `ai-memory.ts` after the agent-distinct `ai-memory-pi.ts` /
+ `ai-memory-omp.ts` split. Following those instructions by hand created the
+ very duplicate-load the split exists to prevent, since each agent loads
+ every `*.ts` in its extensions directory. Documented `--profile` /
+ `OMP_PROFILE` and the `PI_CODING_AGENT_DIR` precedence alongside them.
+ - The lint `stale` threshold is now derived from the operator's `[decay]
+ lambda` instead of a hard-coded 30 days (#426). The rule only fires on
+ episodic pages with zero accesses, and for those the decay score reduces
+ exactly to `salience * exp(-lambda * age)` — the reinforcement term carries
+ `ln(1 + access_count)`, which is zero — so the lint was already measuring
+ decay, just against a constant rather than against `lambda`. Slowing decay
+ made the two diverge: at `lambda = 0.008` real eviction lands near day 201
+ while the lint still called a page stale on day 31, and because a report
+ page is written whenever any finding exists, one page nobody intended to
+ read produced a new `_lint/<date>.md` every day, forever. The threshold is
+ now `0.6 / lambda`, which is **exactly 30 days at the default
+ `lambda = 0.02`** — unchanged for anyone who never tuned decay — and 75
+ days at `0.008`. An invalid or non-positive lambda falls back to the
+ historical constant rather than silencing the rule.
+ - `bin/deploy` now refuses to push a single-architecture build over a tag that
+ already resolves to a multi-architecture manifest (#427). It builds for the
+ architecture of the machine it runs on, so deploying a homelab from an x86
+ workstation to `IMAGE=akitaonrails/ai-memory:latest` replaced the
+ amd64+arm64 manifest CI had published with an amd64-only image, and every
+ arm64 host pulling `:latest` failed with `exec format error`. The shipped
+ `bin/deploy.env.example` also defaulted `IMAGE` to `:latest`, so following
+ the documented setup led straight into it; it now defaults to a private
+ `:homelab` tag and explains that release tags are published by CI only.
+ - `install-hooks` now writes agent-distinct extension filenames
+ (`ai-memory-pi.ts`, `ai-memory-omp.ts`) instead of both agents sharing
+ `ai-memory.ts`, so a Pi install and an OMP install no longer overwrite each
+ other when `PI_CODING_AGENT_DIR` points them at one home. A superseded
+ `ai-memory.ts` is removed only when it carries this tool's generated marker
+ *for that same agent* — a file you wrote yourself, or the other agent's, is
+ left alone and reported. OMP profiles are supported via `--profile` or
+ `OMP_PROFILE`; `PI_CODING_AGENT_DIR` takes precedence over a profile, since
+ it names the agent directory outright.
+
+ Note distinct filenames stop the overwrite but do **not** make a shared
+ directory safe: each agent loads every `*.ts` it finds there, so installing
+ both into one home captures every event twice, once per agent identity.
+ That collision is upstream — both agents read the same environment
+ variable — so `install-hooks` now warns when it detects one and points at
+ the two ways out. (#421)
- `install-hooks --agent pi`, `--agent omp`, and `uninstall` now honor
`PI_CODING_AGENT_DIR`, instead of always writing to `~/.pi/agent/extensions/`
and `~/.omp/agent/extensions/`. Both agents relocate their whole agent