{"version":"2.1.267","anchor":"inbound-message-ingestion-bridge-and-cli-stdin-now-runs-th","canonical_anchor":"inbound-message-ingestion-bridge-and-cli-stdin-now-runs-th","heading":"Inbound message ingestion (bridge and CLI stdin) now runs through a session.receive plugin hook","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/inbound-message-ingestion-bridge-and-cli-stdin-now-runs-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Inbound message ingestion (bridge and CLI stdin) now runs through a session.receive plugin hook\n\nIncoming messages from both Remote Control and the CLI now pass through a `session.receive` plugin hook before being queued\n\n**What**\n\nBoth 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.\n\n**Why**\n\nThis lets plugins intercept and act on incoming messages from either entry point, consistently, before they ever reach the conversation queue.\n\n- Area: Hooks\n- Names: `session.receive`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}