docs: describe gateway injection origin context
This commit is contained in:
@@ -400,6 +400,8 @@ By default, messaging a busy agent redirects its active turn (a running foregrou
|
||||
- `queue` — follow-up messages wait and run as the next turn after the current task finishes.
|
||||
- `steer` — follow-up messages are injected into the current run via `/steer`, arriving at the agent after the next tool call. No interrupt, no new turn. Falls back to `queue` behavior if the agent hasn't started yet.
|
||||
|
||||
Gateway steers (including explicit `/steer`) and active-turn redirects carry the requesting event's available platform, chat, thread, sender, message, profile, and scope identifiers as per-message JSON context. This preserves the original identifiers without changing the session's system prompt or choosing a fallback reply destination. The context is routing data, not authorization or a guarantee of automatic delivery.
|
||||
|
||||
```yaml
|
||||
display:
|
||||
busy_input_mode: steer # or queue, or interrupt (default)
|
||||
|
||||
Reference in New Issue
Block a user