Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge pull request #1696 from akitaonrails/feat/1692-status-consolidation-queue
Fabio Akita148d9bf48a25
diff --cc CHANGELOG.mdindex f30fa165,11588277..82e19d3e--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -11,19 -11,19 +11,30 @@@ version in [`docs/changelog/`](docs/cha## [Unreleased]+ ### Added++ - `GET /admin/status` and `ai-memory status --json` now carry a+ `consolidation` block: the queue counts plus up to 20 `failed_sessions`+ (`session_id`, `attempts`, `failed_at_us`, scrubbed `last_error`), newest+ first. A consolidation run that gives up after its retries now has a+ machine-readable record with the session ids needed to re-run it, instead of+ only a journal line and the `/health` panel's count — which also resets with+ the process. The web health panel's own view stays counts-only, and an older+ server's status shape is unchanged (#1692).+### Fixed+- Codex's own memory-writing agent no longer appears as captured sessions.+ Codex runs a background "memory writing agent" from `$CODEX_HOME/memories`+ (the default `~/.codex/memories`) to consolidate its memory; the hooks+ captured each run as a normal session, so one project of 78 sessions and+ ~2,600 observations existed for work nobody did, and it returned with the+ next run after a purge. Those events are now accepted and stored nowhere,+ recognized by the directory (any `…/.codex/memories`) or by the agent's+ `## Memory Writing Agent` prompt header, and transcript imports+ (`backfill`, the `run` ledger, `recover`) skip them for the same reason+ (#1674).+- `memory_query(answer=true)` now validates model-generated citation pathsagainst the snippets supplied in that request. Unknown paths and pathsshared by distinct page versions withhold the answer, while retrieval hits