Repository navigation
GH#14296: tighten MCP troubleshooting quick reference - #14740
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report SonarCloud: 0 bugs, 0 vulnerabilities, 1 code smells Tue Mar 31 08:09:37 UTC 2026: Code review monitoring started 📈 Current Quality Metrics
Generated on: Tue Mar 31 08:09:39 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report SonarCloud: 0 bugs, 0 vulnerabilities, 1 code smells Tue Mar 31 08:11:14 UTC 2026: Code review monitoring started 📈 Current Quality Metrics
Generated on: Tue Mar 31 08:11:17 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the MCP troubleshooting documentation by refining error causes, adding details on dead schemas, and reorganizing sections for better readability. It also updates the simplification state configuration to track these changes. The review feedback suggests improving consistency in capitalization, adding explicit warnings regarding retrying failed servers to prevent wasting context tokens, and ensuring the pull request number is correctly recorded in the state tracking file for better traceability.
|
|
||
| - **Scripts**: `mcp-diagnose.sh check-all`, `tool-version-check.sh` | ||
| - **Common cause**: Version mismatch (outdated tool with changed MCP command) | ||
| - **Primary cause**: version mismatch (outdated tool, changed MCP command) |
There was a problem hiding this comment.
Capitalize "version" for consistency with the other bullet points in this section (e.g., "Scripts", "Config", "Dead schemas"). Per repository guidelines, important operational details should be formatted as bullet points for clarity.
| - **Primary cause**: version mismatch (outdated tool, changed MCP command) | |
| - **Primary cause**: Version mismatch (outdated tool, changed MCP command) |
References
- For important operational details, format them as bullet points for clarity and readability.
| | "Permission denied" | Missing credentials | Check `~/.config/aidevops/credentials.sh` | | ||
| | "Timeout" | Server not starting | Check Node.js version, run command manually | | ||
| | "unauthorized" | HTTP server instead of MCP | Use correct MCP command (not `serve`) | | ||
| - **Dead schemas (t1682)**: MCP tools can remain listed after startup failure; treat that server as unavailable for the session |
There was a problem hiding this comment.
Consider adding "and do not retry it" to this summary. Per repository guidelines, provide the technical reason (wasting context tokens) and include a warning about the consequences of violating this rule. Also, clarify that MCPs are integrations and not part of the core agent identity.
| - **Dead schemas (t1682)**: MCP tools can remain listed after startup failure; treat that server as unavailable for the session | |
| - **Dead schemas (t1682)**: MCP tools can remain listed after startup failure; treat that server as unavailable for the session and do not retry it. Warning: Retrying consumes unnecessary context tokens for integrations that are not part of the core agent identity. |
References
- For important operational details, format them as bullet points for clarity and readability.
- When documenting critical rules, include a warning about the consequences of violating the rule.
- When documenting restrictions, provide the technical reason behind them to improve understanding.
- When documenting agent identity, clarify that auxiliary tools (like MCPs) are integrations and not part of the core identity.
| ".agents/aidevops/mcp-troubleshooting.md": { | ||
| "hash": "53599e9a3e7d9799a065eb9bc1fe9df2e7dbd1d7", | ||
| "at": "2026-03-31T08:03:51Z", | ||
| "pr": 14740 |
There was a problem hiding this comment.
The pr field should be set to 14296 to match the pull request number from the title. Using null omits useful traceability data for the simplification state tracking.
| "pr": 14740 | |
| "pr": 14296 |
|
…e live ref (#20754) Upstream issue anomalyco/opencode#14740 was auto-closed by stale bot on 2026-04-24 (60d inactivity, not maintainer rejection). PR #14741 remains OPEN with all 9/9 CI green after the v1.2.11 Windows-test fix. Changes: - Status block now names PR #14741 as live tracking surface explicitly - #14740 marked CLOSED-STALE 2026-04-24 with cause - PR CI line refreshed from 6/8 (Windows flake) to 9/9 pass - Added external interest signals (@ualtinok, @tspython) - Added explicit re-file decision with reasoning and reversal conditions - Timeline gains entry 6 for the stale-close event Planning-only cleanup. t1305 stays [x] in TODO.md. Ref #20753
Summary
.agents/configs/simplification-state.jsonso future simplification scans track the file and link back to PR GH#14296: tighten MCP troubleshooting quick reference #14740Testing
bunx markdownlint-cli2 ".agents/aidevops/mcp-troubleshooting.md"python3 -m json.tool ".agents/configs/simplification-state.json" >/dev/nullRuntime Testing
Closes #14296
aidevops.sh v3.5.514 plugin for OpenCode v1.3.9 with gpt-5.4 spent 20m on this as a headless worker.