Agents Remember

vmcp-v2.5.2 scope: mcp Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 1mo AI Agents & Assistants

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent agent-memory ai-agent ai-memory coding-agents mcp-server

Summary

AI summary

Memory carryover API responses are compacted to digest summaries, reducing token counts.

Changes in this release

Type	Severity	Summary	CVE
Feature
Feature	Low	Responses now include per-decision `source_path` digests, capped at 25 with overflow marker. Responses now include per-decision `source_path` digests, capped at 25 with overflow marker. Source: granite4.1:30b@2026-06-10-audit Confidence: low	—
Feature	Low	Added `carriedPaths` field to `memory_carryover_apply` response. Added `carriedPaths` field to `memory_carryover_apply` response. Source: granite4.1:30b@2026-06-10-audit Confidence: low	—
Feature	Low	Included inline `reportPath` in responses. Included inline `reportPath` in responses. Source: granite4.1:30b@2026-06-10-audit Confidence: low	—
Performance	Medium	Compacted `memory_carryover_plan` and `memory_carryover_apply` responses to reduce token usage. Compacted `memory_carryover_plan` and `memory_carryover_apply` responses to reduce token usage. Source: llm_adapter@2026-06-10 Confidence: high	—
Refactor	Low	Moved full records to temporary files under `temp/tool-reports/memory_carryover_/`. Moved full records to temporary files under `temp/tool-reports/memory_carryover_/`. Source: granite4.1:30b@2026-06-10-audit Confidence: low	—

Full changelog

Small patch finishing the response-budget work from 2.5.1: the carryover pair was the last tool surface still returning fat responses.

Changed

memory_carryover_plan / memory_carryover_apply responses compacted (#52): measured live at 3,915 / 7,745 tokens for a 28-file carryover — the apply response contained every candidate record twice, and each record repeated derivable onboarding paths plus an identical per-path reason. Both tools now file the full records under temp/tool-reports/memory_carryover_*/ (keep-last-5 / 7-day retention, secret-redacted) and return per-decision source_path digests (capped at 25 per group with an overflow marker), carriedPaths on apply, and an inline reportPath. Commits, intent note, and counts stay inline. Backward-compatible: the slimmed arrays are flexible envelope detail, same semver posture as 2.5.1.

Known issues under investigation from this release cycle: #53 (worktree_start provider setup is silent for minutes — async visibility planned) and #54 (worktree_start can branch from stale local bases; also silently converts the fast index-copy seed into a full reindex).

Full changes: https://github.com/Foxfire1st/agents-remember-md/pull/55

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track Agents Remember

Get notified when new releases ship.

About Agents Remember

All releases →

Related context

Related tools

Earlier breaking changes

vmcp-v2.9.0 Removed tools direct_closeout_preview and direct_closeout_apply.
vmcp-v2.0.0 `WorkflowKind` enum drops `heavy` and `heavy-task` values.
vmcp-v2.0.0 `skills_install` no longer accepts a `layout` input; installer performs flat copy.
vmcp-v2.0.0 Removed workflows W-01-heavy-task-workflow and W-03-chat-task-workflow.