# Pitfall Log / 踩坑日志

项目：Neal006/mcptail

摘要：发现 30 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：安装坑 - 来源证据：Export a captured call as a regression test。

## 1. 安装坑 · 来源证据：Export a captured call as a regression test

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Export a captured call as a regression test
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/20 | 来源类型 github_issue 暴露的待验证使用条件。

## 2. 安装坑 · 来源证据：Session log rotation: cap per-session file size

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Session log rotation: cap per-session file size
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/13 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

## 4. 配置坑 · 失败模式：configuration: Adapter: Cline

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Adapter: Cline
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Adapter: Cline
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/8 | Adapter: Cline

## 5. 配置坑 · 失败模式：configuration: Adapter: Windsurf

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Adapter: Windsurf
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Adapter: Windsurf
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/6 | Adapter: Windsurf

## 6. 配置坑 · 失败模式：configuration: Adapter: Zed

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Adapter: Zed
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Adapter: Zed
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/7 | Adapter: Zed

## 7. 配置坑 · 失败模式：configuration: Streamable HTTP / SSE transport capture

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Streamable HTTP / SSE transport capture
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Streamable HTTP / SSE transport capture
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/18 | Streamable HTTP / SSE transport capture

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

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

## 9. 运行坑 · 来源证据：UI: light theme

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：UI: light theme
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/11 | 来源类型 github_issue 暴露的待验证使用条件。

## 10. 运行坑 · 来源证据：UI: search / filter in the timeline

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：UI: search / filter in the timeline
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/10 | 来源类型 github_issue 暴露的待验证使用条件。

## 11. 维护坑 · 失败模式：migration: Add GPT and Gemini input prices to pricing.json

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Add GPT and Gemini input prices to pricing.json
- 对用户的影响：Developers may hit a documented source-backed failure mode: Add GPT and Gemini input prices to pricing.json
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/9 | Add GPT and Gemini input prices to pricing.json

## 12. 维护坑 · 失败模式：migration: Session diffing — compare two runs of the same server

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Session diffing — compare two runs of the same server
- 对用户的影响：Developers may hit a documented source-backed failure mode: Session diffing — compare two runs of the same server
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/21 | Session diffing — compare two runs of the same server

## 13. 维护坑 · 失败模式：migration: mcptail clear — prune recorded sessions

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: mcptail clear — prune recorded sessions
- 对用户的影响：Developers may hit a documented source-backed failure mode: mcptail clear — prune recorded sessions
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/12 | mcptail clear — prune recorded sessions

## 14. 维护坑 · 来源证据：Session diffing — compare two runs of the same server

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：Session diffing — compare two runs of the same server
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/21 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

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

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

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

## 18. 安全/权限坑 · 来源证据：OpenTelemetry exporter

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：OpenTelemetry exporter
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/19 | 来源类型 github_issue 暴露的待验证使用条件。

## 19. 安全/权限坑 · 来源证据：Streamable HTTP / SSE transport capture

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Streamable HTTP / SSE transport capture
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/Neal006/mcptail/issues/18 | 来源类型 github_issue 暴露的待验证使用条件。

## 20. 能力坑 · 失败模式：capability: Export a captured call as a regression test

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Export a captured call as a regression test
- 对用户的影响：Developers may hit a documented source-backed failure mode: Export a captured call as a regression test
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/20 | Export a captured call as a regression test

## 21. 能力坑 · 失败模式：capability: Session log rotation: cap per-session file size

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Session log rotation: cap per-session file size
- 对用户的影响：Developers may hit a documented source-backed failure mode: Session log rotation: cap per-session file size
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/13 | Session log rotation: cap per-session file size

## 22. 能力坑 · 失败模式：capability: UI: keyboard navigation (j/k + enter) in the timeline

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: UI: keyboard navigation (j/k + enter) in the timeline
- 对用户的影响：Developers may hit a documented source-backed failure mode: UI: keyboard navigation (j/k + enter) in the timeline
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/15 | UI: keyboard navigation (j/k + enter) in the timeline

## 23. 能力坑 · 失败模式：capability: UI: light theme

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: UI: light theme
- 对用户的影响：Developers may hit a documented source-backed failure mode: UI: light theme
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/11 | UI: light theme

## 24. 能力坑 · 失败模式：capability: UI: search / filter in the timeline

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: UI: search / filter in the timeline
- 对用户的影响：Developers may hit a documented source-backed failure mode: UI: search / filter in the timeline
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/10 | UI: search / filter in the timeline

## 25. 能力坑 · 失败模式：conceptual: README translation: हिन्दी (hi)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: README translation: हिन्दी (hi)
- 对用户的影响：Developers may hit a documented source-backed failure mode: README translation: हिन्दी (hi)
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/17 | README translation: हिन्दी (hi)

## 26. 能力坑 · 失败模式：conceptual: README translation: 中文 (zh-CN)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: README translation: 中文 (zh-CN)
- 对用户的影响：Developers may hit a documented source-backed failure mode: README translation: 中文 (zh-CN)
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/16 | README translation: 中文 (zh-CN)

## 27. 运行坑 · 失败模式：performance: Export a session as HAR

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: Export a session as HAR
- 对用户的影响：Developers may hit a documented source-backed failure mode: Export a session as HAR
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/14 | Export a session as HAR

## 28. 运行坑 · 失败模式：performance: OpenTelemetry exporter

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: OpenTelemetry exporter
- 对用户的影响：Developers may hit a documented source-backed failure mode: OpenTelemetry exporter
- 证据：failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/19 | OpenTelemetry exporter

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

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

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

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