The new gateway stream-event protocol added format_tool_event to BasePlatformAdapter in NousResearch#37250. The base implementation renders every ToolCallChunk as an emoji+name+preview string that the gateway then ships through the adapter normal send path.

For Telegram that becomes a single edited bubble. Nostr has no in-place message editing — NIP-09 is event deletion, not editing — so every tool progress event would land as its own NIP-17 gift-wrap published to all relays. A multi-tool turn would flood the recipient.

Override the hook to return None so the dispatcher eats tool events entirely and only the final agent response reaches the user. Nostr is the first adapter to take advantage of the override; the base default matches today pre-protocol behavior for adapters that have not yet migrated.

Add a dm_only per-platform streaming mode so Telegram can keep native draft streaming for private chats and DM topics while group/forum chats stay on final-send delivery.

This preserves existing boolean override behavior and keeps the change config-driven: display.platforms.telegram.streaming can be false, true, or dm_only/private_only.

Context:

- Hermes was updated to main with PR NousResearch#37250 included.

- Group/topic Telegram chats previously hit edit-rate and final-message failure modes when streaming was enabled.

- The local runtime needs DM streaming enabled while group delivery remains non-streaming.

Add a dm_only per-platform streaming mode so Telegram can keep native draft streaming for private chats and DM topics while group/forum chats stay on final-send delivery.

This preserves existing boolean override behavior and keeps the change config-driven: display.platforms.telegram.streaming can be false, true, or dm_only/private_only.

Context:

- Hermes was updated to main with PR NousResearch#37250 included.

- Group/topic Telegram chats previously hit edit-rate and final-message failure modes when streaming was enabled.

- The local runtime needs DM streaming enabled while group delivery remains non-streaming.

The new gateway stream-event protocol added format_tool_event to BasePlatformAdapter in NousResearch#37250. The base implementation renders every ToolCallChunk as an emoji+name+preview string that the gateway then ships through the adapter normal send path.

For Telegram that becomes a single edited bubble. Nostr has no in-place message editing — NIP-09 is event deletion, not editing — so every tool progress event would land as its own NIP-17 gift-wrap published to all relays. A multi-tool turn would flood the recipient.

Override the hook to return None so the dispatcher eats tool events entirely and only the final agent response reaches the user. Nostr is the first adapter to take advantage of the override; the base default matches today pre-protocol behavior for adapters that have not yet migrated.

…atting parity (NousResearch#37250)

Introduce a typed agent→gateway delivery contract so the gateway (not the
agent) decides how each streaming event is rendered per platform. Moves toward
smart-agent/smart-gateway separation while reproducing today's behavior exactly
in the base class.

- gateway/stream_events.py: typed event vocabulary (MessageChunk/Stop,
  Commentary, ToolCallChunk/Finished, LongToolHint, GatewayNotice).
- gateway/stream_dispatch.py: GatewayEventDispatcher routes events through the
  adapter; adapters can eat events they can't render (e.g. tool chrome on
  plain-text platforms).
- gateway/platforms/base.py: render_message_event + format_tool_event default
  hooks reproduce the historical emoji/preview tool formatting and consumer
  delegation 1:1; adapters override for native rendering.
- gateway/platforms/telegram.py: send_draft now applies MarkdownV2 (format_message
  + parse_mode) with a plain-text fallback on BadRequest, fixing the jarring
  raw-text→formatted shift when the draft finalizes as a real sendMessage.
- gateway/config.py: default streaming transport edit → auto. Safe globally:
  adapters without draft support report supports_draft_streaming()==False and
  transparently use edit, so only Telegram DMs gain native drafts.

Presentation-only contract — nothing rendered here is persisted to conversation
history, preserving cache/message-flow invariants.

The new gateway stream-event protocol added format_tool_event to BasePlatformAdapter in NousResearch#37250. The base implementation renders every ToolCallChunk as an emoji+name+preview string that the gateway then ships through the adapter normal send path.

For Telegram that becomes a single edited bubble. Nostr has no in-place message editing — NIP-09 is event deletion, not editing — so every tool progress event would land as its own NIP-17 gift-wrap published to all relays. A multi-tool turn would flood the recipient.

Override the hook to return None so the dispatcher eats tool events entirely and only the final agent response reaches the user. Nostr is the first adapter to take advantage of the override; the base default matches today pre-protocol behavior for adapters that have not yet migrated.

Add a dm_only per-platform streaming mode so Telegram can keep native draft streaming for private chats and DM topics while group/forum chats stay on final-send delivery.

This preserves existing boolean override behavior and keeps the change config-driven: display.platforms.telegram.streaming can be false, true, or dm_only/private_only.

Context:

- Hermes was updated to main with PR NousResearch#37250 included.

- Group/topic Telegram chats previously hit edit-rate and final-message failure modes when streaming was enabled.

- The local runtime needs DM streaming enabled while group delivery remains non-streaming.

Add a dm_only per-platform streaming mode so Telegram can keep native draft streaming for private chats and DM topics while group/forum chats stay on final-send delivery.

This preserves existing boolean override behavior and keeps the change config-driven: display.platforms.telegram.streaming can be false, true, or dm_only/private_only.

Context:

- Hermes was updated to main with PR NousResearch#37250 included.

- Group/topic Telegram chats previously hit edit-rate and final-message failure modes when streaming was enabled.

- The local runtime needs DM streaming enabled while group delivery remains non-streaming.

The new gateway stream-event protocol added format_tool_event to BasePlatformAdapter in NousResearch#37250. The base implementation renders every ToolCallChunk as an emoji+name+preview string that the gateway then ships through the adapter normal send path.

For Telegram that becomes a single edited bubble. Nostr has no in-place message editing — NIP-09 is event deletion, not editing — so every tool progress event would land as its own NIP-17 gift-wrap published to all relays. A multi-tool turn would flood the recipient.

Override the hook to return None so the dispatcher eats tool events entirely and only the final agent response reaches the user. Nostr is the first adapter to take advantage of the override; the base default matches today pre-protocol behavior for adapters that have not yet migrated.