AgentDB Retrieval Security Layer (ADR-377)
Closes #2516 / tracked in #2873: AgentDB's retrieval and write paths had zero certified defenses against memory poisoning (undefended attack success 93β100% per SMSR, arXiv:2606.12703). Full 3-phase implementation shipped in #2874, all off by default until independently benchmarked.
AgentDbRetrievalGuard(@claude-flow/memory) β filters HNSW retrieval results throughToolOutputGuardrail's OWASP LLM01/LLM08 pattern scan before context assembly.CLAUDE_FLOW_RETRIEVAL_GUARD/_STRICT.MemoryPoisonForensics(@claude-flow/hooks) β rolling-window z-score anomaly detection on AgentDB write sequences (write-interval, content-length).CLAUDE_FLOW_POISON_FORENSICS=0to disable.McpCallerIdentity(@claude-flow/security) β Ed25519 per-invocation capability tokens.CLAUDE_FLOW_MCP_CALLER_AUTH, off by default pending a follow-on key-distribution ADR.
Also in this release:
- #2871 β consolidated 49 stale dream-cycle research proposals (open since 2026-05-29, never merged) into ADR-334 through ADR-376, resolving the ADR-147/ADR-179/ADR-320 numbering collisions along the way.
- #2872 β recovered ADR-377 itself from an abandoned dream-cycle branch that never got a PR opened for it.
31 new tests across the three touched packages, zero regressions (memory 451, hooks 145, security 570 full suites re-run clean).
Packages
@claude-flow/cli@3.33.0claude-flow@3.33.0ruflo@3.33.0
π€ Generated with Claude Code