What
Both the Remote Control bridge's inbound-message path and the main CLI's stdin/user-message loop now run incoming messages through the session.receive plugin hook before turning them into a queued prompt. If the hook reports the message as consumed, it's dropped before being enqueued instead of being added to the conversation.
Why
This lets plugins intercept and act on incoming messages from either entry point, consistently, before they ever reach the conversation queue.
Names in the bundlesession.receive
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up session.receive, on Use the mods API.
`session.receive` and `session.send` let a mod observe the messages. Return `next(e)` from both to pass each message through unchanged:plugins/mods/api see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up session.receive, on Use the mods API.