Grayscale/nanobot
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

fix(bus): preserve legacy outbound metadata events

Browse Source
This commit is contained in:
Xubin Ren
2026-07-01 20:17:00 +08:00
parent 03be51ade5
commit c78421cf16
4 changed files with 253 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/channel-plugin-guide.md
+1 -1
View File
@@ -262,7 +262,7 @@ class OutboundMessage:
event: object | None # typed runtime/UI event; usually inspect with isinstance()
```
Runtime/UI semantics live on `msg.event`. Plugin-authored outbound messages should not rely on legacy metadata flags such as `_progress`, `_stream_delta`, `_stream_end`, `_reasoning_delta`, `_turn_end`, or `_goal_status`; they are treated as ordinary metadata, not parsed as runtime events.
Runtime/UI semantics live on `msg.event`. Plugin-authored outbound messages should use typed events instead of legacy metadata flags such as `_progress`, `_stream_delta`, `_stream_end`, `_reasoning_delta`, `_turn_end`, or `_goal_status`. nanobot still accepts those old flags as a compatibility bridge for existing in-process extensions, but new plugin code should not add fresh dependencies on them.
## Streaming Support