You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description\n\nCurrently, tools handle errors in different ways. Some return error objects with a format like while others throw exceptions that are caught and converted to error messages. As seen in Issue #78, when a tool crashes unexpectedly, it can lead to unhandled exceptions that propagate to the user.\n\n## Proposed Solution\n\n1. Standardize error handling across all tools by having them throw exceptions for error conditions rather than returning error objects.\n2. Modify the tool executor to catch all exceptions from tool execution and convert them to a standardized error response format.\n3. This approach will:\n - Make tool implementations simpler (just throw errors, don't worry about formatting them)\n - Ensure consistent error handling across all tools\n - Prevent crashes from propagating to users\n - Leverage the standard JavaScript error handling mechanism\n\n## Implementation Steps\n\n1. Update to catch all exceptions and convert them to a standard error format\n2. Modify tools like to throw exceptions instead of returning error objects\n3. Update any tools that currently return error objects to use the exception mechanism instead\n4. Ensure the error format in responses is consistent across all tools\n\n## Related Issues\n\n- Fixes #78 (TextEditor tool crash)
