Skip to content

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

Rust

Merge issue/1511-gitdir-fsync

AkitaOnRails7d47bfeca46c
diff --cc CHANGELOG.md
index 9bb7cf99,db24fcdb..bac8e0d4
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -223,46 -223,17 +223,57 @@@ version in [`docs/changelog/`](docs/cha
relay and wiki sync companions take the same `rustls-webpki` bump.
### Fixed
+- Memory health no longer counts a link from a superseded or TTL-expired page
+ version as a reference. A page whose only inbound link was removed by a later
+ edit was reported as linked, because the old version's `links` row survives
+ the edit and is repointed at the new latest id, so the orphan count and
+ detail list disagreed with the page's own backlinks.
+ ([#1526](https://github.com/akitaonrails/ai-memory/pull/1526))
+
+- A `title:` or `body:` search filter whose term carries a second colon, such
+ as `title:10:30`, now keeps its column. FTS5 read the inner `10` as a column
+ name and rejected the whole expression, so the query degraded to the quoted
+ bag of words: the filter was dropped and every column was searched for the
+ literal word `title`.
+ ([#1521](https://github.com/akitaonrails/ai-memory/pull/1521))
+- `memory_query` no longer discards `as_of` on a global query. An explicit
+ `global` with `as_of` is now refused, as the error message always claimed,
+ and a repo on `[recall] default_global` no longer broadens an `as_of` query
+ to global and answers it with present-day rows.
+ ([#1519](https://github.com/akitaonrails/ai-memory/pull/1519))
+
+- A `429` or `5xx` from a token endpoint is now a transient provider error
+ rather than an auth failure. The Copilot token exchange, which GitHub
+ rate-limits per account, and the shared `openai-oauth`/OIDC refresh both
+ reported throttling as a credential problem, so the fallback chain stopped
+ instead of trying the next provider and the operator was told to log in
+ again for a grant that was never rejected.
+ ([#1520](https://github.com/akitaonrails/ai-memory/pull/1520))
+
+- The Gemini embedder now cuts a long input to the same 8 KB head as the
+ OpenAI, Copilot and local embedders. It sent the whole page, while the
+ default `gemini-embedding-001` takes at most 2,048 input tokens, and a
+ refused page embedding is only logged, so a long page could end up with no
+ vector. Voyage is unchanged: its API shortens an over-long input itself.
+ ([#1513](https://github.com/akitaonrails/ai-memory/pull/1513))
+
+- `memory_auto_improve` now reports an exhausted implicit queue — every
+ completed session already has a review run — as invalid params rather than an
+ internal error, matching `memory_consolidate` for the same dead end. A client
+ no longer reads the routine end of the queue as a server fault and retries it.
+ ([#1518](https://github.com/akitaonrails/ai-memory/pull/1518))
+
+ - The wiki's git objects and refs are now synced to disk. libgit2 renamed them
+ into place without fsync, so a power loss could keep a ref naming a commit
+ whose object was never written, and every later checkpoint failed. Every
+ repository handle ai-memory opens now turns on `core.fsyncObjectFiles` from
+ `.git/ai-memory.gitconfig`, a file only libgit2 reads, so `.git/config` is
+ untouched and the git CLI shows no deprecation warning; an explicit `false`
+ in `.git/config` is kept. Startup logs an `ERROR` when `HEAD` does not
+ resolve to a readable commit, and a failed bootstrap auto-commit is logged
+ instead of dropped. `docs/lifecycle-ops.md` describes the repair for a
+ history already damaged.
+ ([#1511](https://github.com/akitaonrails/ai-memory/issues/1511))
- Reserved local-embedding capacity for interactive search queries instead of
allowing concurrent page writes and backfill work to occupy every inference
slot. Excess queries fall back immediately to non-vector retrieval, and a