This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+10 more
Summary
AI summarySignal now has ownership, TTL, and status tracking (pending/claimed/acked/expired) with new MCP methods.
Full changelog
Agent Memory Bridge v0.4.0
This release turns the bridge into a cleaner framework and gives signal a real coordination lifecycle.
What changed
Neutral core defaults
- core defaults now use neutral profile settings instead of Cole-shaped titles, actors, and namespaces
- profile-specific wording now sits in config instead of leaking into the framework runtime
- the default shared namespace is now
global
Signal lifecycle
signalis no longer just append-only state- added MCP support for:
claim_signalack_signal
- signals now support:
- lease ownership
- TTL / expiry
- visible statuses:
pending,claimed,acked,expired
Storage cleanup
- signal lifecycle helpers now live in a dedicated module
- export rendering now lives in its own module
- storage behavior now reflects the two-channel model more clearly
Docs and setup
- README and README.zh-CN were rewritten around the v0.4 shape
- setup now explains the neutral profile config
- roadmap now reflects the next stage: proof, selection, and composition
MCP surface
The public MCP tools are now:
storerecallbrowsestatsforgetpromoteclaim_signalack_signalexport
Verification
- full test suite:
57 passed
Why this release matters
Agent Memory Bridge is not trying to be a general memory platform.
It is a small MCP-native bridge for coding-agent workflows, with two separate channels:
- durable knowledge in
memory - coordination events in
signal
v0.4.0 makes that split much more real in both the runtime and the public surface.
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
About zzhang82/Agent-Memory-Bridge
MCP-native, local-first memory for coding agents that turns coding sessions into reusable engineering memory: decisions, gotchas, and domain knowledge.
Related context
Beta — feedback welcome: [email protected]