Skip to content

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

Rust

Merge PR #908 into main

AkitaOnRails25ce9109a675
diff --cc CHANGELOG.md
index 09c91ba7,3d5170e9..4144bb33
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -38,15 -38,14 +38,23 @@@ and this project adheres to [Semantic V
feedback-loop guard stays non-overridable. (#894)
### Fixed
+- The default log filter's `rmcp=warn` cap (#894) no longer raises rmcp
+ above a quieter `log_level`. A target directive beats the global level
+ either way, so with `log_level = "error"` or `"off"` the cap re-enabled the
+ SDK's warnings the operator had silenced; it now only applies when
+ `log_level` is louder than `warn`. (#896)
+- A session with no usable prompt is titled `Session <id>` rather than
+ `stop` or `session-end`. Once #895 skipped tool-family labels in the title
+ fallback, the next candidate in a real session was the kind name the router
+ stores for an untitled lifecycle event. (#897)
+ - A wiki page with CRLF line endings is parsed as having frontmatter again.
+ `markdown::parse` only matched the fence lines with a bare `\n`, so a page
+ a Windows editor saved, or one `core.autocrlf=true` checked out, was treated
+ as body-only: `reindex`/the watcher indexed it without its `tier`,
+ `pinned`, `expires_at` and `entities` (a pinned page became decay-eligible),
+ the title came from the filename, and the one-shot OKF file pass wrote a
+ second frontmatter block above the authored one. The parser now accepts
+ `---\r\n` fences and leaves the body's line endings untouched. (#908)
- A manual `memory_consolidate` now reconciles the session's durable
consolidation job row. The MCP handler wrote the page directly through the
consolidator without touching `session_consolidation_jobs`, so a session