CLAUDE-MEM V13.1.0 SHIPS AN EVENT-SOURCED AGENT PIPELINE WITH POSTGRES, BULLMQ, AND MULTI-PROVIDER JOBS
thedotmack/claude-mem v13.1.0 lands a Postgres+BullMQ event pipeline, audited job flow, and safer session concurrency for AI coding agents. The new release wir...
thedotmack/claude-mem v13.1.0 lands a Postgres+BullMQ event pipeline, audited job flow, and safer session concurrency for AI coding agents.
The new release wires agent_event → outbox jobs → workers → observation rows with idempotent enqueue, request-id propagation, and a structured audit log. It exposes POST /v1/events and session start/end, plus job list/retry/cancel, with per-team/project scoping and Anthropic/OpenAI/Google providers release.
Legacy clients keep working via compatibility shims, and race conditions on concurrent session start are handled via 23505 catch-and-refetch. A Docker/Compose stack and CLI streamline local ops (same release).
If you’re standardizing agent workflows, this aligns with MCP-style patterns and Claude Code plugin workflows plugins and complements emerging permission/guardrail practices permissions.
Gives teams a concrete, auditable event-to-observation pattern for running agents in production.
Reduces flaky session handling with idempotency, request IDs, and concurrent start race fixes.
-
terminal
Spin up the Docker stack, POST /v1/events twice with the same idempotency key, and verify single enqueue, end-to-end request-id propagation, and audit rows.
-
terminal
Simulate concurrent POST /v1/sessions/start with the same externalSessionId and confirm 23505 handling returns the winning session instead of 500s; check structured error bodies.
Legacy codebase integration strategies...
- 01.
Route existing workers through the legacy shims and validate parity while auditing Postgres failures return JSON, not HTML 500s.
- 02.
Map team/project scoping to current auth model, and log provider errors by class for SLOs.
Fresh architecture paradigms...
- 01.
Adopt the event-sourced pipeline as the backbone for agent jobs with built-in audit, retries, and multi-provider support.
- 02.
Standardize on MCP-style interfaces and extend via Claude Code plugins for code review or release flows.
Get daily CLAUDE-CODE + SDLC updates.
- Practical tactics you can ship tomorrow
- Tooling, workflows, and architecture notes
- One short email each weekday