Skip to content

Fix smoke-copilot: call Serena tools directly instead of inferring availability from mcp-inspect#1249

Merged
lpcox merged 2 commits intomainfrom
copilot/debug-smoke-copilot-failure
Feb 21, 2026
Merged

Fix smoke-copilot: call Serena tools directly instead of inferring availability from mcp-inspect#1249
lpcox merged 2 commits intomainfrom
copilot/debug-smoke-copilot-failure

Conversation

Copy link
Contributor

Copilot AI commented Feb 21, 2026

The Smoke Copilot workflow failed because the agent called agenticworkflows-mcp-inspect as an uninstructed pre-check for Serena availability. That call returns -32603 (Serena is already running in the MCP gateway — it can't be cold-started for inspection), and the agent incorrectly treated that failure as proof the tools were absent — never attempting serena-activate_project directly despite all 23 Serena tools being registered and available.

Changes

  • smoke-copilot.md step 3: Rewrite the Serena test instructions to:
    • Require calling serena-activate_project directly with no pre-flight checks
    • Explicitly state that mcp-inspect failure does not indicate tool unavailability
    • Only report Serena as unavailable if the direct tool call itself errors

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • example.com
    • Triggering command: /tmp/go-build2906290365/b279/launcher.test /tmp/go-build2906290365/b279/launcher.test -test.testlogfile=/tmp/go-build2906290365/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo (dns block)
  • invalid-host-that-does-not-exist-12345.com
    • Triggering command: /tmp/go-build2906290365/b264/config.test /tmp/go-build2906290365/b264/config.test -test.testlogfile=/tmp/go-build2906290365/b264/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo 8m9dy2lhN .12/x64/as (dns block)
  • nonexistent.local
    • Triggering command: /tmp/go-build2906290365/b279/launcher.test /tmp/go-build2906290365/b279/launcher.test -test.testlogfile=/tmp/go-build2906290365/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo (dns block)
  • slow.example.com
    • Triggering command: /tmp/go-build2906290365/b279/launcher.test /tmp/go-build2906290365/b279/launcher.test -test.testlogfile=/tmp/go-build2906290365/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo (dns block)
  • this-host-does-not-exist-12345.com
    • Triggering command: /tmp/go-build2906290365/b288/mcp.test /tmp/go-build2906290365/b288/mcp.test -test.testlogfile=/tmp/go-build2906290365/b288/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo 64/src/maps/iter.go x_amd64/compile (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>[agentics] Smoke Copilot failed</issue_title>
<issue_description>### Workflow Failure

Workflow: Smoke Copilot
Branch: main
Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/22262473176

Action Required

Option 1: Assign this issue to agent using agentic-workflows

Assign this issue to the agentic-workflows agent to automatically debug and fix the workflow failure.

Option 2: Manually invoke the agent

Debug this workflow failure using the agentic-workflows agent:

/agent agentic-workflows debug the agentic workflow smoke-copilot failure in https://github.com/github/gh-aw-mcpg/actions/runs/22262473176

Generated from Smoke Copilot

  • expires on Feb 28, 2026, 7:05 PM UTC

Comments on the Issue (you are @copilot in this section)


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

…ut pre-checking via mcp-inspect

Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Copilot AI changed the title [WIP] Debug workflow failure in Smoke Copilot Fix smoke-copilot: call Serena tools directly instead of inferring availability from mcp-inspect Feb 21, 2026
@lpcox lpcox marked this pull request as ready for review February 21, 2026 19:44
Copilot AI review requested due to automatic review settings February 21, 2026 19:44
@lpcox lpcox merged commit 3f82de6 into main Feb 21, 2026
4 checks passed
@lpcox lpcox deleted the copilot/debug-smoke-copilot-failure branch February 21, 2026 19:44
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Smoke Copilot agentic workflow instructions to avoid false negatives when validating Serena tool availability (by calling Serena tools directly rather than relying on mcp-inspect pre-checks).

Changes:

  • Rewrites the “Serena MCP Testing” instructions to require a direct serena-activate_project call.
  • Clarifies that failures from indirect diagnostics (like mcp-inspect) are not proof Serena is unavailable.
  • Keeps the follow-up Serena validation step (serena-find_symbol) to confirm symbol discovery works.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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
Copy link

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

serena-activate_project likely doesn’t take a path argument. In the Serena MCP server tests, project activation is called with relative_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 (likely relative_path, probably set to "." / repo root) or omit the argument if the tool defaults to the configured project root.

Suggested change
- 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
- Call the `serena-activate_project` tool DIRECTLY with `relative_path: "."` — 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

Copilot uses AI. Check for mistakes.
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
Copy link

Copilot AI Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This text forbids mcp-inspect, but the failure described in the PR comes from the prefixed tool name (agenticworkflows-mcp-inspect) used in routed mode. Consider explicitly calling out agenticworkflows-mcp-inspect here as well, otherwise the agent may still try that “diagnostic” pre-check.

Suggested change
- 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

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[agentics] Smoke Copilot failed

3 participants