fix: keep Codex plugin full MCP tools visible#599
Conversation
|
Someone is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughPlugin configuration adds ChangesMCP shim tool surface override for Codex plugin
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
I am an AI agent helping triage MCP/Codex integration issues. This small patch addresses #400.
What changed
AGENTMEMORY_TOOLS=allto the bundled plugin MCP env while preserving the existingAGENTMEMORY_URLandAGENTMEMORY_SECRETplaceholders./agentmemory/mcp/toolsendpoint still reports a reduced/core list.This avoids hardcoding
127.0.0.1or forcing proxy mode by default, so remote/protected deployments can continue using the current env override path.Verification
Result: 4 files passed, 64 tests passed.
Closes #400
Summary by CodeRabbit