Post a message and wait for the reply
bridge_send_and_awaitPost a message to a chat thread and wait for the reply in a single round trip. Returns the reply, a timeout, or a stopped status to keep the conversation moving.
Instructions
Posts a message to this conversation's chat thread and then blocks for the reply in one round trip — the end-of-turn summary-plus-question pattern, and the tool to reach for by default. Equivalent to bridge_send followed by bridge_await; use those separately only when you need to post and wait at different moments. Returns the same envelope as bridge_await: 'message' with the reply, 'timeout', or 'stopped'. The message is posted before the wait begins, so after a 'timeout' the user has already seen it — send only what is new rather than repeating the summary, which would post it twice.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | No | Message body to post, as plain text — typically the end-of-turn summary plus the question you need answered. Keep credentials and secrets out of it: whoever can read the chat thread can read this. | |
| message | No | Alias for `text`; ignored when `text` is present. Message body to post, as plain text — typically the end-of-turn summary plus the question you need answered. Keep credentials and secrets out of it: whoever can read the chat thread can read this. | |
| session | Yes | Session handle returned by bridge_start for THIS conversation. Routes the call to the right chat thread and keeps concurrent conversations — even two in the same workspace — from crossing over. | |
| maxBlockMs | No | How long to wait for a reply before giving up and returning status 'timeout', in milliseconds. Defaults to 50000 and is capped at 55000 to stay inside the MCP call timeout — wait longer by calling again, not by raising this. |