Summary

• Guard against undefined params in ipcBridge.conversation.sendMessage.provider callback
• WebSocket messages without a data payload (e.g. bypassPermissions) cause TypeError: Cannot destructure property 'conversation_id' of 'undefined'
• Returns { success: false, msg: 'Missing request parameters' } instead of crashing

Sentry Issue

ELECTRON-FK — 85 events in 1 day, escalating

• Error: TypeError: Cannot destructure property 'conversation_id' of 'undefined' as it is undefined.
• Culprit: src/process/bridge/conversationBridge.ts:397 (sendMessage.provider)
• Affected release: [email protected]

Root Cause

The WebSocketManager parses incoming messages as { name, data }. When a message has a valid name but no data field, data is undefined. This flows through adapter.ts → @office-ai/platform bridge → sendMessage.provider callback, where destructuring { conversation_id, files, ...other } from undefined throws a TypeError.

Fix

Add a null/undefined check at the top of the provider callback before destructuring.

Test Plan

• Unit test: undefined params returns error response
• Unit test: null params returns error response
• Unit test: valid params proceeds normally
• bunx tsc --noEmit passes
• bun run lint:fix — no errors
• bun run test — all relevant tests pass (pre-existing previewFileWatch.dom.test.ts failures unrelated)