# Pitfall Log / 踩坑日志

项目：vheins/local-memory-mcp

摘要：发现 37 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：安装坑 - 失败模式：installation: feat: full-local natural language codebase search (codebase_search tool)。

## 1. 安装坑 · 失败模式：installation: feat: full-local natural language codebase search (codebase_search tool)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: feat: full-local natural language codebase search (codebase_search tool)
- 对用户的影响：Developers may fail before the first successful local run: feat: full-local natural language codebase search (codebase_search tool)
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/45 | feat: full-local natural language codebase search (codebase_search tool)

## 2. 安装坑 · 失败模式：installation: feat: tambahkan monorepo workspace seperti turbo repo

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: feat: tambahkan monorepo workspace seperti turbo repo
- 对用户的影响：Developers may fail before the first successful local run: feat: tambahkan monorepo workspace seperti turbo repo
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/42 | feat: tambahkan monorepo workspace seperti turbo repo

## 3. 安装坑 · 失败模式：installation: perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste
- 对用户的影响：Developers may fail before the first successful local run: perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/50 | perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste

## 4. 安装坑 · 来源证据：feat: full-local natural language codebase search (codebase_search tool)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：feat: full-local natural language codebase search (codebase_search tool)
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/45 | 来源类型 github_issue 暴露的待验证使用条件。

## 5. 安装坑 · 来源证据：fix: nested .gitignore not respected during file discovery

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：fix: nested .gitignore not respected during file discovery
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/57 | 来源类型 github_issue 暴露的待验证使用条件。

## 6. 安装坑 · 来源证据：perf: synchronous lstatSync + low concurrency bottlenecks in indexing pipeline

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：perf: synchronous lstatSync + low concurrency bottlenecks in indexing pipeline
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/51 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 7. 安装坑 · 来源证据：perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：perf: tree-sitter grammar WASMs eager-loaded at startup — 30MB+ waste
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/50 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 8. 配置坑 · 可能修改宿主 AI 配置

- 严重度：medium
- 证据强度：source_linked
- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- 证据：capability.host_targets | https://github.com/vheins/local-memory-mcp | host_targets=mcp_host, claude, cursor

## 9. 配置坑 · 失败模式：configuration: feat: unified neural network graph for memory, codebase, and task visualization

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: feat: unified neural network graph for memory, codebase, and task visualization
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: feat: unified neural network graph for memory, codebase, and task visualization
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/58 | feat: unified neural network graph for memory, codebase, and task visualization

## 10. 配置坑 · 失败模式：configuration: perf: missing composite indexes on (owner, repo) — full table scans on frequent queries

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: perf: missing composite indexes on (owner, repo) — full table scans on frequent queries
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: perf: missing composite indexes on (owner, repo) — full table scans on frequent queries
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/49 | perf: missing composite indexes on (owner, repo) — full table scans on frequent queries

## 11. 配置坑 · 失败模式：configuration: v0.20.4 — Multi-language Parsing

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v0.20.4 — Multi-language Parsing
- 对用户的影响：Upgrade or migration may change expected behavior: v0.20.4 — Multi-language Parsing
- 证据：failure_mode_cluster:github_release | https://github.com/vheins/local-memory-mcp/releases/tag/v0.20.4 | v0.20.4 — Multi-language Parsing

## 12. 配置坑 · 来源证据：perf: dashboard export loads entire DB into memory — OOM risk

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：perf: dashboard export loads entire DB into memory — OOM risk
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/48 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 13. 配置坑 · 来源证据：perf: missing composite indexes on (owner, repo) — full table scans on frequent queries

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：perf: missing composite indexes on (owner, repo) — full table scans on frequent queries
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/49 | 来源类型 github_issue 暴露的待验证使用条件。

## 14. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://github.com/vheins/local-memory-mcp | README/documentation is current enough for a first validation pass.

## 15. 运行坑 · 来源证据：fix: double vector computation in StandardEntity.checkConflicts

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：fix: double vector computation in StandardEntity.checkConflicts
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/56 | 来源类型 github_issue 暴露的待验证使用条件。

## 16. 运行坑 · 来源证据：perf: RealVectorStore ONNX model blocks first request — lazy init timeout risk

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：perf: RealVectorStore ONNX model blocks first request — lazy init timeout risk
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/52 | 来源类型 github_issue 暴露的待验证使用条件。

## 17. 运行坑 · 来源证据：perf: search_symbols loads ALL symbols into memory — OOM risk on large repos

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：perf: search_symbols loads ALL symbols into memory — OOM risk on large repos
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/46 | 来源类型 github_issue 暴露的待验证使用条件。

## 18. 运行坑 · 来源证据：refactor: normalizeToolArguments duplicated between router.ts and tools/index.ts

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：refactor: normalizeToolArguments duplicated between router.ts and tools/index.ts
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/54 | 来源类型 github_issue 暴露的待验证使用条件。

## 19. 运行坑 · 运行可能依赖外部服务

- 严重度：medium
- 证据强度：source_linked
- 发现：项目说明出现 external service/cloud/webhook/database 等运行依赖关键词。
- 对用户的影响：本地安装成功不等于能力可用，外部服务不可用会阻断体验。
- 证据：packet_text.keyword_scan | https://github.com/vheins/local-memory-mcp | matched external service / cloud / webhook / database keyword

## 20. 维护坑 · 失败模式：migration: perf: coding_standards uses LIKE %term% without FTS5 — full table scan on every search

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: perf: coding_standards uses LIKE %term% without FTS5 — full table scan on every search
- 对用户的影响：Developers may hit a documented source-backed failure mode: perf: coding_standards uses LIKE %term% without FTS5 — full table scan on every search
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/53 | perf: coding_standards uses LIKE %term% without FTS5 — full table scan on every search

## 21. 维护坑 · 失败模式：migration: v0.21.0 — Codebase Search NL + FTS5 Standards

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: v0.21.0 — Codebase Search NL + FTS5 Standards
- 对用户的影响：Upgrade or migration may change expected behavior: v0.21.0 — Codebase Search NL + FTS5 Standards
- 证据：failure_mode_cluster:github_release | https://github.com/vheins/local-memory-mcp/releases/tag/v0.21.0 | v0.21.0 — Codebase Search NL + FTS5 Standards

## 22. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://github.com/vheins/local-memory-mcp | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/vheins/local-memory-mcp | no_demo; severity=medium

## 24. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://github.com/vheins/local-memory-mcp | no_demo; severity=medium

## 25. 安全/权限坑 · 来源证据：feat: unified neural network graph for memory, codebase, and task visualization

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：feat: unified neural network graph for memory, codebase, and task visualization
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/58 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 26. 安全/权限坑 · 来源证据：perf: StubVectorStore upsert stores zero-filled vectors — redundant computation on search

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：perf: StubVectorStore upsert stores zero-filled vectors — redundant computation on search
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/55 | 来源类型 github_issue 暴露的待验证使用条件。

## 27. 安全/权限坑 · 来源证据：perf: coding_standards uses LIKE %term% without FTS5 — full table scan on every search

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：perf: coding_standards uses LIKE %term% without FTS5 — full table scan on every search
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/vheins/local-memory-mcp/issues/53 | 来源类型 github_issue 暴露的待验证使用条件。

## 28. 运行坑 · 失败模式：performance: fix: double vector computation in StandardEntity.checkConflicts

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: fix: double vector computation in StandardEntity.checkConflicts
- 对用户的影响：Developers may hit a documented source-backed failure mode: fix: double vector computation in StandardEntity.checkConflicts
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/56 | fix: double vector computation in StandardEntity.checkConflicts

## 29. 运行坑 · 失败模式：performance: fix: nested .gitignore not respected during file discovery

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: fix: nested .gitignore not respected during file discovery
- 对用户的影响：Developers may hit a documented source-backed failure mode: fix: nested .gitignore not respected during file discovery
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/57 | fix: nested .gitignore not respected during file discovery

## 30. 运行坑 · 失败模式：performance: perf: RealVectorStore ONNX model blocks first request — lazy init timeout risk

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: perf: RealVectorStore ONNX model blocks first request — lazy init timeout risk
- 对用户的影响：Developers may hit a documented source-backed failure mode: perf: RealVectorStore ONNX model blocks first request — lazy init timeout risk
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/52 | perf: RealVectorStore ONNX model blocks first request — lazy init timeout risk

## 31. 运行坑 · 失败模式：performance: perf: StubVectorStore upsert stores zero-filled vectors — redundant computation on search

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: perf: StubVectorStore upsert stores zero-filled vectors — redundant computation on search
- 对用户的影响：Developers may hit a documented source-backed failure mode: perf: StubVectorStore upsert stores zero-filled vectors — redundant computation on search
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/55 | perf: StubVectorStore upsert stores zero-filled vectors — redundant computation on search

## 32. 运行坑 · 失败模式：performance: perf: dashboard export loads entire DB into memory — OOM risk

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: perf: dashboard export loads entire DB into memory — OOM risk
- 对用户的影响：Developers may hit a documented source-backed failure mode: perf: dashboard export loads entire DB into memory — OOM risk
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/48 | perf: dashboard export loads entire DB into memory — OOM risk

## 33. 运行坑 · 失败模式：performance: perf: synchronous lstatSync + low concurrency bottlenecks in indexing pipeline

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: perf: synchronous lstatSync + low concurrency bottlenecks in indexing pipeline
- 对用户的影响：Developers may hit a documented source-backed failure mode: perf: synchronous lstatSync + low concurrency bottlenecks in indexing pipeline
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/51 | perf: synchronous lstatSync + low concurrency bottlenecks in indexing pipeline

## 34. 运行坑 · 失败模式：performance: perf: write lock contention on memory-acknowledge and hit-count tools

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: perf: write lock contention on memory-acknowledge and hit-count tools
- 对用户的影响：Developers may hit a documented source-backed failure mode: perf: write lock contention on memory-acknowledge and hit-count tools
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/47 | perf: write lock contention on memory-acknowledge and hit-count tools

## 35. 运行坑 · 失败模式：performance: refactor: normalizeToolArguments duplicated between router.ts and tools/index.ts

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: refactor: normalizeToolArguments duplicated between router.ts and tools/index.ts
- 对用户的影响：Developers may hit a documented source-backed failure mode: refactor: normalizeToolArguments duplicated between router.ts and tools/index.ts
- 证据：failure_mode_cluster:github_issue | https://github.com/vheins/local-memory-mcp/issues/54 | refactor: normalizeToolArguments duplicated between router.ts and tools/index.ts

## 36. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://github.com/vheins/local-memory-mcp | issue_or_pr_quality=unknown

## 37. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://github.com/vheins/local-memory-mcp | release_recency=unknown