You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`send` and `dm` accept an optional `streamingBehavior` field that tells the receiving bridge how urgently to surface the message:
211
+
212
+
| Value | Meaning | Pi bridge | Claude Code bridge | Drain bridges (MCP, Codex) |
213
+
|---|---|---|---|---|
214
+
|`steer`| Act now — react at the next decision boundary |`deliverAs: "steer"`|`[STEER]` prefix + `meta.streamingBehavior`|`[STEER]` prefix on drain |
215
+
|`followUp`| Act when idle — wait until the current task finishes |`deliverAs: "followUp"`|`[FOLLOWUP]` prefix + `meta.streamingBehavior`|`[FOLLOWUP]` prefix on drain |
216
+
|`info`| Whenever convenient (default, matches current behaviour) | Informational buffer | No prefix | No prefix |
217
+
218
+
When `streamingBehavior` is absent, each bridge falls back to its existing heuristic: actionable events (DMs, room messages, invites) are treated as `steer`; status changes and membership events are treated as `info`.
219
+
220
+
**Limitations on non-native harnesses**: Claude Code's channel protocol is a single-lane push — there is no runtime mechanism to force a mid-call interrupt. The `[STEER]` and `[FOLLOWUP]` markers are visible in the session and structured `meta.streamingBehavior` carries the intent, but acting on them is down to the receiving agent. The pi bridge honours the hint natively.
0 commit comments