feat: Stream tool progress messages to Open WebUI#4032
Closed
sroecker wants to merge 1 commit into
Closed
Conversation
Add tool execution progress visibility in Open WebUI streaming responses: - Add stream_delta_callback calls in _execute_tool_calls_sequential for tool completion messages (both concurrent and sequential paths) - Add _has_stream_consumers() check to include tool_gen_callback in streaming path decision - Add tool name length validation to prevent truncated names (<3 chars) - Stream tool messages as inline content using emoji icons Changes: - run_agent.py: Tool completion callbacks and streaming consumer check - api_server.py: Remove redundant _on_tool_progress, use direct callback Fixes codex review findings: - Streaming consumer registration - Truncated tool name handling
teknium1
added a commit
that referenced
this pull request
Mar 31, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR #4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
Contributor
teknium1
added a commit
that referenced
this pull request
Mar 31, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR #4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
angelburgosrosado
pushed a commit
to angelburgosrosado/hermes-agent
that referenced
this pull request
Apr 27, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR NousResearch#4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
02356abc
pushed a commit
to 02356abc/hermes-agent
that referenced
this pull request
May 14, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR NousResearch#4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
olympus-terminal
pushed a commit
to olympus-terminal/hermes-agent
that referenced
this pull request
May 16, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR NousResearch#4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
gweeteve
pushed a commit
to gweeteve/hermes-agent
that referenced
this pull request
Jun 2, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR NousResearch#4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
Egavasyug
pushed a commit
to Egavasyug/hermes-agent
that referenced
this pull request
Jun 10, 2026
Wire the existing tool_progress_callback through the API server's streaming handler so Open WebUI users see what tool is running. Uses the existing 3-arg callback signature (name, preview, args) that fires at tool start — no changes to run_agent.py needed. Progress appears as inline markdown in the SSE content stream. Inspired by PR NousResearch#4032 by sroecker, reimplemented to avoid breaking the callback signature used by CLI and gateway consumers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds visibility for Hermes Agent tool execution in Open WebUI streaming responses. Users will now see inline tool progress messages (e.g., "🐍 exec python code...", "📖 read file...") as the agent works.
Changes
run_agent.py
stream_delta_callbackcalls in_execute_tool_calls_sequentialfor tool completion messages_has_stream_consumers()to includetool_gen_callbackcheck (fixes streaming path decision)api_server.py
_on_tool_progresscallbackstream_delta_callbackTesting
Examples
Users will see messages like:
Notes
stream: true)