CLAUDE‑MEM 12.1 SHIPS "KNOWLEDGE AGENTS" WITH HTTP APIS; MASSGEN 0.1.74 HARDENS MCP — LOCAL AGENT STACKS GET PRODUCTION LEGS
Two open-source releases make private, queryable knowledge bases and agent workflows far easier to stand up and operate. Claude‑mem’s latest release adds a ful...
Two open-source releases make private, queryable knowledge bases and agent workflows far easier to stand up and operate.
Claude‑mem’s latest release adds a full "Knowledge Agents" lifecycle — build, prime, query, and rebuild corpora from your activity — with 6 MCP tools, 8 /api/corpus/* endpoints, a 1M‑token renderer, auto‑reprime, and security hardening like path‑traversal and prompt‑injection defenses release notes. It ships docs and an e2e suite covering the full corpus workflow.
MassGen 0.1.74 improves its checkpoint MCP server, tightens subprocess isolation, and fixes duplicate tool calls across ChatCompletions and Response backends, including MiniMax on OpenRouter release. Paired with the "self‑evolving" wiki pattern for persistent knowledge explainer and local‑first building blocks like on‑device transcription assistants write‑up, teams can now assemble private, robust agent systems without renting a SaaS brain.
You can stand up private, queryable corpora with a tested API surface instead of gluing prompts to ad hoc files.
Security and isolation improvements reduce common footguns (path traversal, prompt injection, duplicate tool calls) before production.
-
terminal
Build a small corpus from internal runbooks or tickets via /api/corpus/*, then measure answer quality, latency, and token usage with the 1M‑token renderer.
-
terminal
Run red‑team prompts against the primed session to validate the new injection defenses and auto‑reprime behavior under expired sessions.
Legacy codebase integration strategies...
- 01.
Pipe existing sources (Confluence, Git repos, ticketing, incident timelines) into corpus builders with a redaction step for PII/secrets.
- 02.
Gate corpus build/query behind service auth and audit logging; enforce per‑team corpora with RBAC and retention policies.
Fresh architecture paradigms...
- 01.
Design per‑service, ephemeral corpora with TTLs and rebuild hooks from CI to keep answers fresh without retraining.
- 02.
Adopt MCP‑native tools early so agents can call uniform backends (checkpoint flows, subprocess isolation) across environments.