fix(mcp): honor custom config paths#477
Merged
intellectronica merged 2 commits intoMay 24, 2026
Merged
Conversation
intellectronica
deleted the
intellectronica/456-single-owner-mcp-custom-paths
branch
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
1 participant
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.
Closes #456.\n\n## Summary\n- let the apply engine own Codex/OpenCode MCP writes during normal apply\n- resolve MCP destinations from output_path_config before native defaults\n- ensure OpenCode creates parent directories for custom instruction/config paths\n- add integration coverage proving Codex/OpenCode write only custom MCP config paths\n\n## Verification\n- npx jest tests/integration/mcp-custom-config-path.test.ts --runInBand\n- npm run lint\n- npm test -- --runInBand\n- npm run build