run-llama/chat-ui
1
0
Fork 0
mirror of https://github.com/run-llama/chat-ui.git synced 2026-07-22 03:45:20 -04:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Make AgentWorkflows deployed on LlamaDeploy work with useChatWorkflow #25

New Issue
Closed
opened 2026-02-16 02:17:44 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 02:17:44 -05:00
Owner
Copy Link
Copy Source

Originally created by @thucpn on GitHub (Jul 7, 2025).

Originally assigned to: @thucpn on GitHub.

Description

As we're not using the backend (llamaindexserver) any more - it no longer transforms ToolCallResult events into source_nodes events for the frontend. Instead we're using now LlamaDeploy with useChatWorkflow which sends raw ToolCall and ToolCallResult events directly for a deployed AgentWorkflow to chat-ui.

We need to implement the transformation logic on the frontend side to maintain the ability to display source nodes and their URLs.

✅ Tasks

  • Listen to and correctly handle both ToolCall and ToolCallResult events from the stream.
  • Transform ToolCallResult into source_nodes event format for the UI.
  • Construct valid URLs for each source node in ToolCallResult.tool_output.
  • Add an example that works with local files (add API route that serve the files)
  • Add an example that works with LlamaCloud (the API route must download and cache the LlamaCloud files)
Originally created by @thucpn on GitHub (Jul 7, 2025). Originally assigned to: @thucpn on GitHub. ## Description As we're not using the backend (`llamaindexserver`) any more - it no longer transforms `ToolCallResult` events into `source_nodes` events for the frontend. Instead we're using now `LlamaDeploy` with `useChatWorkflow` which sends raw `ToolCall` and `ToolCallResult` events directly for a deployed AgentWorkflow to `chat-ui`. We need to implement the transformation logic on the frontend side to maintain the ability to display source nodes and their URLs. --- ## ✅ Tasks - [x] Listen to and correctly handle both `ToolCall` and `ToolCallResult` events from the stream. - [x] Transform `ToolCallResult` into `source_nodes` event format for the UI. - [x] Construct valid URLs for each source node in `ToolCallResult.tool_output`. - [x] Add an example that works with local files (add API route that serve the files) - [x] Add an example that works with LlamaCloud (the API route must download and cache the LlamaCloud files)
yindo closed this issue 2026-02-16 02:17:44 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/chat-ui#25
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?