v0.3.45: fixes for organization invites, custom tool execution#1234
v0.3.45: fixes for organization invites, custom tool execution#1234waleedlatif1 merged 2 commits intomainfrom
Conversation
waleedlatif1
commented
Sep 3, 2025
- fix(team): fix organization invitation URL for teams (fix(team): fix organization invitation URL for teams #1232)
- fix(rce): always use VM over RCE for custom tools (fix(rce): always use VM over RCE for custom tools #1233)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Greptile Summary
This PR contains two targeted bug fixes addressing issues with organization invitations and custom tool execution.
The first change fixes organization invitation URLs by simplifying their structure from a query parameter pattern (/invite/organization?id={id}) to a cleaner path parameter pattern (/invite/{id}). This affects the email rendering functions in the POST handler for organization invitations, making invitation URLs more concise and following better REST conventions. The change maintains the same invitation ID while just changing how it's encoded in the URL, suggesting the frontend routing has been updated to handle invitations with this simpler structure.
The second change ensures custom tools always use local VM execution instead of E2B (remote code execution) by adding a !isCustomTool condition to the execution decision logic. This modification forces custom tools to bypass E2B execution and use the local VM environment, which provides consistent variable and environment variable resolution. The change is necessary because custom tools require special parameter handling where their parameters are made directly accessible as variables in the execution context, and E2B execution has different variable resolution patterns that could lead to inconsistent behavior.
Both changes integrate well with the existing codebase architecture - the invitation URL change aligns with the existing invitation system while improving URL structure, and the custom tool execution change maintains the existing execution logic while ensuring proper parameter handling for custom tools.
Confidence score: 5/5
- This PR is extremely safe to merge with virtually no risk of production issues
- Score reflects simple, well-targeted changes that fix specific bugs without introducing complexity or side effects
- No files require special attention as both changes are straightforward and isolated
2 files reviewed, no comments