The plain-English version
Messages exchanged between separate processes through defined communication mechanisms. Payload structure should be documented.
Why it matters
Desktop processes need contracts for requests, responses, caller identity, and errors.
Let’s make it click
A window sends a typed request to load preferences and receives only supported preference fields.
Vibe Bro’s heads-up
An unrestricted message handler can accidentally expose privileged operations to unintended callers.
The docs behind it
Documentation links checked .
Editorial review · October 28, 2026
Supported: Electron documents developer-defined message channels, asynchronous invoke responses, and serializable payload limits. The validation guidance is supported.