-
Notifications
You must be signed in to change notification settings - Fork 13
Fix smoke-copilot: call Serena tools directly instead of inferring availability from mcp-inspect #1249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix smoke-copilot: call Serena tools directly instead of inferring availability from mcp-inspect #1249
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -88,8 +88,9 @@ timeout-minutes: 15 | |||||||||
| 1. **GitHub MCP Testing**: Review the last 2 merged pull requests in ${{ github.repository }} | ||||||||||
| 2. **Safe Inputs GH CLI Testing**: Use the `safeinputs-gh` tool to query 2 pull requests from ${{ github.repository }} (use args: "pr list --repo ${{ github.repository }} --limit 2 --json number,title,author") | ||||||||||
| 3. **Serena MCP Testing**: | ||||||||||
| - Use the `serena-activate_project` tool to initialize the workspace at `${{ github.workspace }}` and verify it succeeds (do NOT use bash to run go commands - use Serena's MCP tools or the safeinputs-go/safeinputs-make tools from the go-make shared workflow) | ||||||||||
| - After initialization, use the `serena-find_symbol` tool to search for symbols and verify that at least 3 symbols are found in the results | ||||||||||
| - Call the `serena-activate_project` tool DIRECTLY with `path: "${{ github.workspace }}"` — do NOT use `mcp-inspect` or any other diagnostic tool to pre-check availability; just call the tool and observe whether it succeeds or returns an error | ||||||||||
| - A failure of `mcp-inspect` or any other indirect check does NOT indicate that Serena tools are unavailable; only report Serena as unavailable if the direct `serena-activate_project` call itself returns an error | ||||||||||
|
Comment on lines
+91
to
+92
|
||||||||||
| - Call the `serena-activate_project` tool DIRECTLY with `path: "${{ github.workspace }}"` — do NOT use `mcp-inspect` or any other diagnostic tool to pre-check availability; just call the tool and observe whether it succeeds or returns an error | |
| - A failure of `mcp-inspect` or any other indirect check does NOT indicate that Serena tools are unavailable; only report Serena as unavailable if the direct `serena-activate_project` call itself returns an error | |
| - Call the `serena-activate_project` tool DIRECTLY with `path: "${{ github.workspace }}"` — do NOT use `mcp-inspect`, `agenticworkflows-mcp-inspect`, or any other diagnostic tool to pre-check availability; just call the tool and observe whether it succeeds or returns an error | |
| - A failure of `mcp-inspect`, `agenticworkflows-mcp-inspect`, or any other indirect check does NOT indicate that Serena tools are unavailable; only report Serena as unavailable if the direct `serena-activate_project` call itself returns an error |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
serena-activate_projectlikely doesn’t take apathargument. In the Serena MCP server tests, project activation is called withrelative_path(e.g.,{"relative_path": "go_project"}), so this instruction may cause the smoke workflow to fail when the agent follows it. Update the instruction to use the correct argument name (likelyrelative_path, probably set to "." / repo root) or omit the argument if the tool defaults to the configured project root.