Phase 6 (partial): Claude Desktop config re-verified, re-verification procedure documented - #8
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The changes are documentation-only, internally consistent with the repo’s tool naming (search_guidelines), and improve clarity without affecting runtime behavior.
Pull request overview
Updates the repository’s README to make MCP client setup and ongoing client-compatibility verification more explicit and reproducible, with a focus on Claude Desktop configuration and keeping the compatibility table falsifiable over time.
Changes:
- Replaces the Claude Desktop compatibility row with a more precise “config format re-checked” claim.
- Adds an explicit Claude Desktop
claude_desktop_config.jsonsnippet plus platform config paths and an “absoluteargspath” note. - Documents a concrete “Re-verifying these rows” procedure (including checking that the client actually calls
search_guidelines).
File summaries
| File | Description |
|---|---|
| README.md | Adds Claude Desktop config details and documents a re-verification procedure for compatibility claims. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Merged
Phase 6, as far as it can go without a GUI. - Claude Desktop's config format re-checked against the current MCP quickstart: `mcpServers` with command/args is unchanged. The README now carries the actual JSON and both platform config paths instead of only linking out, and notes that args must be absolute — the most common reason a stdio server silently fails to start. Its compatibility row is updated to say the format was re-checked, while still stating it was not driven against a live client. - Added a "Re-verifying these rows" procedure: how to promote a documentation-only row to verified, including the check that actually matters — ask something only the guidelines answer, and confirm the tool is called rather than the model answering from general knowledge — and where Copilot in VS Code reports whether it picked the server up. Phase 6.1 — driving this against live GitHub Copilot Chat and capturing a dated screenshot — is NOT done and cannot be done from here: it needs an interactive VS Code session with an authenticated Copilot subscription. The compatibility table continues to mark those rows documentation-only, which remains accurate. The procedure above is what is left for a human to run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
luciocabrera
force-pushed
the
phase6/verification
branch
from
September 2, 2026 07:02
278f7e4 to
222d89c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #7. This phase is deliberately incomplete — see below.
Done
mcpServerswithcommand/argsis unchanged. The README now carries the actual JSON and both platform config paths rather than only linking out, plus the note thatargspaths must be absolute — the most common cause of a stdio server silently failing to start.Not done — needs you
Phase 6.1 (live GitHub Copilot Chat verification with a dated screenshot) cannot be done from this environment. It needs an interactive VS Code session with an authenticated Copilot subscription; I can't drive the chat UI or capture a screenshot headlessly.
The compatibility table therefore still marks the Copilot rows documentation-only, which is accurate rather than optimistic — deliberately, since asserting verification I didn't perform is the exact failure Phase 1 was created to fix.
The README now contains the config and the procedure, so it should be a couple of minutes: build, drop the
.vscode/mcp.jsonsnippet in, ask Copilot a guidelines question, screenshot, update the row's date and method.🤖 Generated with Claude Code