Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge release/2.7 into PR #1127
AkitaOnRails37fac02bb051
diff --cc CHANGELOG.mdindex 14c4d539,27a529e3..695f3c51--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -8,11 -8,18 +8,23 @@@ and this project adheres to [Semantic V## [Unreleased]### Added+- Added the `cursor` LLM provider. Consolidation calls the logged-in Cursor+ Agent CLI (`agent --print --mode ask`) so a Cursor subscription can drive+ summaries without an API key. The default model is `cursor-grok-4.6-high`+ ("Grok 4.6"). `AI_MEMORY_CURSOR_AGENT` overrides the binary. The provider never passes- `--yolo` or `--force`, because the prompt is captured session text.++ `--yolo` or `--force`, because the prompt is captured session text. (#1127)+ - Added `ai-memory recover` and a bounded local recovery journal for server+ outages. Offline managed launches now record only uniquely correlated native+ session locators; recovery quarantines overlapping spool entries before exact+ `/hook/batch` transcript replay, journals harnesses without transcript export+ as spool-only without calling their exporter, retains bounded recovery dedup+ keys with their sessions,+ fails closed on terminal drops, and lets only the original owner finish an+ expired unsuperseded managed run through exact idempotent replay. Backfill+ and recovery replay now use reserved `recovery_*` idempotency keys, so+ re-running `backfill --force` over sessions imported by ai-memory ≤2.6.0 (or+ plain-backfilling a recovery-replayed session) can duplicate those older+ observations. (#1125)### Fixed- Fixed the hook spool charging a spooled event's retry budget while the