Memory Sidecar v3.5.1 lands as a focused operational hardening release for the public agent-agnostic memory layer. If you’ve been running earlier iterations in production with multi-agent systems, you know the friction: dangling connections from failed sessions, unbounded retries hammering storage backends, and inconsistent transaction windows when multiple agents write simultaneously. This release doesn’t introduce new storage engines or retrieval strategies—it locks down the seams where real-world deployments bleed availability.
Operational Improvements
The core target is fault isolation and deterministic cleanup. Two concrete changes drive this:
Session Scoped Graceful Shutdown
Previously, when an agent task died ungracefully, the sidecar held onto memory handles until a timeout forced closure. In v3.5.1, every session lock is tied to a unique ephemeral token, and the sidecar’s heartbeat goroutine now detects stale tokens within half the lease interval. The shutdown path emits a final checkpoint before releasing storage, preventing orphaned write buffers.
