Remove legacy tool naming mode#24
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
💤 Files with no reviewable changes (6)
📝 WalkthroughWalkthroughRemoves the ChangesRemove DEVSPACE_TOOL_NAMING and legacy tool names
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Comment |
…ames-only # Conflicts: # src/config.test.ts # src/config.ts # src/server.ts # src/ui/card-types.ts # src/ui/workspace-app.tsx
Summary
DEVSPACE_TOOL_NAMINGand its configuration parsingExisting
DEVSPACE_TOOL_NAMINGvalues are ignored after upgrading. MCP clients receiveopen_workspace,read,write,edit,bash, and the mode-dependent short tools. Pi SDK adapter identifiers remain unchanged because they are internal API names.Verification
npm testnpm run typechecknpm run buildSummary by CodeRabbit
New Features
Bug Fixes
Documentation