codebase-memory-mcp Shipped v0.10.0, Then v0.10.1 Seventeen Hours Later Because Every Discovery Tool Returned an Empty {} to Claude Code
DeusData's codebase-memory-mcp (38,513 stars) released v0.10.0 on 2026-08-10 with a wire-size optimization that stopped duplicating tool payloads into `structuredContent` while every tool still declared a permissive `outputSchema` — so under the MCP spec, `search_graph`, `trace_path`, `query_graph`, `get_architecture`, `search_code`, and `detect_changes` all returned `{}` to schema-honoring clients like Claude Code and Codex. Issue #1522 landed within hours, and the verification sweep found two more bugs sharing the same shape (empty result plus success status): 7+ pipelined requests overflowed an 8-frame queue and killed the server with exit 1, and `config get` returned an empty string with exit 0 for both unset and misspelled keys. The maintainers publicly conceded their own tests 'pinned the broken behavior as correct' at unit, binary-smoke, and CI level — the pipeline was green because it agreed with the bug.
Source
↳ Follow the thread