Skip to content

Agents Remember

v0.8.0 Bugfix

This release fixes issues for SREs watching stability and regressions.

✓ 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

Bug fixes and stability improvements in Agents Remember.

Full changelog

Release Notes
Agents Remember, May 12, 2026
Changes since v0.7.0

Big Tickets

  1. C-11 adds memory carryover between branches

    A new C-11-memory-carryover-from-branch workflow can carry richer onboarding memory from one branch into another once the corresponding code has landed.

    This gives Agents Remember a safer path for preserving useful memory work from feature branches without pretending branch-local knowledge is automatically valid everywhere.

  2. Memory ledgers are now branchless

    The canonical memory.md schema is now ar-memory-ledger/v1.

    The ledger no longer stores trackedCodeBranch or memoryBranch. Compatibility is defined by the thing that actually matters: the mapping from code commit to memory commit.

    Legacy ar-memory-branch-ledger/v1 files remain readable, but newly written ledgers use the simpler branchless format.

  3. C-08 memory resolution is more reliable

    The coordination context resolver was tightened around memory-root and onboarding-root resolution.

    Downstream workflows now get cleaner, more explicit context for shared memory roots, coordination roots, task roots, temp roots, ledger paths, and cross-repo allowances.

  4. Heavy workflow skills moved into a phase-based layout

    The heavy workflow is now organized under W-01-heavy-task-workflow/skills/ by phase.

    Creation, research, synthesis, design, planning, implementation, review, and closing support are easier to find and reason about as separate workflow surfaces.

  5. Workflow routing is clearer

    Core routing guidance was tightened across AGENTS.md files and workflow docs.

    Chat-mode work now has a dedicated W-03-chat-task-workflow, durable task work remains under W-02-light-task-workflow, and heavy phased work remains explicit under W-01-heavy-task-workflow.

  6. Documentation and onboarding were cleaned up

    README, FAQ, settings examples, system guidance, and onboarding templates were refreshed to match the current terminology.

    The repo now consistently favors coordination_root, memory_root, code_repository_name, and code_repository_root language over older management-root wording.

Upgrade Notes

  • Existing branch-metadata ledgers still parse, but new writes use ar-memory-ledger/v1.
  • Any automation that reads trackedCodeBranch or memoryBranch from memory.md should switch to commit mapping fields.
  • Direct closeout still checks the actual checked-out code and memory branches where needed; it just no longer treats branch names as durable ledger identity.
  • Links or scripts pointing directly at old heavy-workflow phase paths may need to be updated to the new nested skill layout.

Validation

  • Focused worktree support suite passes: 39 tests.
  • Commit range reviewed: v0.7.0..3274222.
  • Summary since v0.7.0: 71 files changed, with 2330 insertions and 7119 deletions.

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

Track Agents Remember

Get notified when new releases ship.

Sign up free

About Agents Remember

All releases →

Related context

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.

Beta — feedback welcome: [email protected]