Skip to content

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

Rust

Merge pull request #1371 from viniciusdsandrade/fix/mcp-expired-page-annotation

AkitaOnRails97097addc3dc
diff --cc CHANGELOG.md
index de12ba3a,a11d20cb..be945cd6
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -12,80 -12,13 +12,87 @@@ version in [`docs/changelog/`](docs/cha
## [Unreleased]
### Fixed
+- `ai-memory auth login openai-oauth` and `auth login copilot` no longer print
+ a failed endpoint's whole response body. Error bodies are bounded, scrubbed
+ of secrets and terminal control sequences, then capped for display; provider
+ errors, including OIDC login and refresh, use the same ordering so a secret
+ at the display boundary is still redacted. (#1359)
+- Fixed OIDC device login and refresh sending credential-bearing requests to
+ non-TLS endpoints. Issuers and advertised or persisted device/token endpoints
+ must now use `https` outside loopback, and authentication requests do not
+ follow redirects. Plain `http` remains available for local test issuers on
+ `localhost`, `127.0.0.1` and `::1`. (#1354)
+- Fixed `install-instructions` printing a false "Claude Code reads <file> instead
+ of AGENTS.md" note when `$HOME` is reached through a symlink. The home
+ `.claude/CLAUDE.md` skip now compares with the same canonicalising
+ `paths_match` helper the import check uses, so a symlinked home matches its
+ resolved path. (#1345)
+- Corrected stale claims in `docs/comparison.md` and `docs/competitive-parity.md`
+ that said Windows has no service step and the Windows install is experimental.
+ The 3.1 `install.ps1` + `setup` Windows service step is shipped production,
+ not experimental; the "3.0 (unreleased)" observation-stream note is corrected
+ to reflect the released 3.0 line. (#1271)
+- Made the executable auto-improvement eval policy server-owned. Manual CLI and
+ HTTP reviews now use `[auto_improve.eval]` from the server process, and legacy
+ requests that try to supply an `eval` object fail closed with an upgrade
+ message.
+- Made managed cross-harness continuation survive quota exhaustion without a
+ voluntary handoff. The startup packet now places its server-authored resume
+ directive outside the untrusted transcript fence, and refreshed
+ `CLAUDE.md` / `AGENTS.md` routing tells an incoming agent that "continue",
+ "resume", and "pick up where we left off" must consult the private
+ `AI_MEMORY_PREVIOUS_SESSION_HISTORY` dossier when the managed-run variables
+ are present. The dossier remains untrusted evidence and stays local to the
+ launcher machine.
+- Fixed unbounded memory use in consolidation and auto-improve for long
+ sessions: both paths now read a bounded projection of the session's
+ observations instead of loading every row, keeping the LLM input
+ byte-identical. Sessions with no observations in the consolidator's target
+ scope (purged or foreign) are refused before any work, exactly as empty
+ sessions were before. (#1363)
+- Fixed the session page's uncapped `## Prompts` list. Above 500 prompts the
+ page now lists the first 250 titles and the last 250, numbered by their real
+ position, with one line between them saying how many were left out. The
+ store reads at most 500 titles for it, and the page's prompt count and the
+ digest stats still report the true total. (#1349)
+- Fixed auto-improve approvals that failed because a `reject`-policy admission
+ webhook was unreachable, timed out, rate-limited or answered 5xx being
+ stored as rejections. The proposal is still marked `failed`, but the outage
+ no longer enters the rejection buffer, so later reviews are not told to
+ avoid a proposal nobody refused and rejection telemetry counts only real
+ refusals. (#1358)
+- Fixed consolidation persisting non-page `relations:` targets in YAML
+ frontmatter on disk. Raw titles containing dots, directory paths, or stemless
+ `.md` strings in `relations:` were previously written into frontmatter and
+ retained by `prune_relations` when `extract_relation_links` returned an empty
+ list, causing the wiki watcher to emit repeated warnings on every
+ reconciliation pass. Targets are now validated through `extract_relation_links`
+ before frontmatter assembly and during relation pruning. (#1353, #1366)
+- Consolidation now also drops well-shaped same-project `relations:` targets
+ that name no existing page. Relations among pages in the same atomic batch
+ remain valid, and ordinary same-project body wikilinks may still point to a
+ page that will be written later. (#1353)
+- Verified target latest status and expiration in
+ `ReaderPool::contradiction_edges`, so a contradiction pointing at a
+ tombstoned or expired page is reported as unresolved instead of active, and
+ expired source pages do not emit contradiction findings. (#1367)
+- Verified target latest status and expiration in
+ `ReaderPool::dangling_cross_project_links`, so cross-project links to
+ tombstoned or expired pages are reported as dangling instead of resolved,
+ and expired source pages do not emit dangling link findings. (#1368)
+- Fixed the `/web` project tree and its recent-activity list, the namespace
+ listing, and the `/api/v1` `pages` list and legacy `recent` array showing
+ pages whose `expires_at` TTL had passed, which search, `memory_recent`, the
+ incremental `recent` form and page history already hid. A project move and
+ the curator still see every current page, and an exact-path read of an
+ expired page still answers. (#1369)
+ - Fixed `memory_read_page` returning a page whose `expires_at` TTL had passed
+ with nothing to say so. The TTL design keeps an exact-path read answering for
+ such a page while `memory_query`, `memory_recent` and the briefing hide it,
+ and promised the response would carry `expired: true`; the flag was never
+ written. The response now carries `expired: true` for an expired page, on
+ both the markdown and the DB-fallback branch, and is unchanged for a live
+ one. (#1371)
## [3.1.0] - 2026-10-16