This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
Affected surfaces
Summary
AI summarySidecar management defaults to per‑repo folders with opt‑in cross‑repo linking.
Full changelog
The assumption has changed to support the simpler and most likely way more common case of single repo
sidecars instead of assuming that people want to put their sidecars of all their repos into a central folder.
Now each repo can own their own sidecar folder which makes versioning a lot easier out of the gate. You can still
create cross-repo relationsships but it is an opt-in function now. Otherwise it is assumed that you stay within the repo.
The advanced option is still there to organise all repos sidecars in a central folder or mix and match strategies. So some repos
can use the shared system and some can stay local.
Breaking Changes
- Default behavior now assumes each repository owns its own sidecar folder; cross‑repo relationships are opt‑in instead of assumed.
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 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.
Beta — feedback welcome: [email protected]