Fix serena MCP context to use engine-specific values instead of hardcoded "codex" #10761
+44
−25
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.
Smoke test run 21112904973 failed on serena Go test with
go: command not found. Root cause: serena MCP server was hardcoded to--context codexregardless of engine, causing wrong runtime environment.Changes
Core fix:
pkg/workflow/mcp-config-serena.go: AddedengineIDparameter torenderSerenaMCPConfigWithOptions(), uses engine-specific context with fallback to "codex"pkg/workflow/mcp_renderer.go: AddedEngineIDfield toMCPRendererOptions, passes engine ID to serena rendererEngine renderers:
claude_mcp.go,codex_mcp.go,copilot_mcp.goto passe.idwhen creating rendererTests:
"codex"as engine ID parameterResult
Workflows now use correct serena context:
--context copilot--context claude--context codexNote: GitHub MCP test failure in same run is unrelated (Copilot agent not providing required tool parameters - requires Copilot CLI team investigation).
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.