mirror of
https://github.com/open-webui/docs.git
synced 2026-11-05 01:38:13 +00:00
[GH-ISSUE #1438] Backend-Controlled API Flow: user message disappears from UI after step 2 trigger assistant completion and refresh. #171
Labels
No labels
bug
documentation
documentation
duplicate
enhancement
enhancement
good first issue
good first issue
good first issue
help wanted
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/docs#171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @vrzh on GitHub (Sep 23, 2026).
Original GitHub issue: https://github.com/open-webui/docs/issues/1438
Hi, thank you for the awesome project!
I am following the Backend-Controlled API Flow instructions. I hope this is the correct venue, there was a previous similar issue posted here https://github.com/open-webui/docs/issues/1175.
I understand that "Future versions may introduce changes in behavior or API structure." so I am hoping as part of the answer would be some info on how I can figure out what the correct calls are (if there are changes in the future).
When I complete step 2 (trigger assistant completion) and then refresh the web UI, the user message disappears from the UI. I am on the latest version
0.11.4.UI view of chat after step 1 (as expected):

UI view of chat after step 2 (as expected both user and assistant messages can be seen):
UI view after refreshing the UI in the browser (problem - only the assistant message can be seen, user message is missing):

For ease of testing I combined step 1 and step 2 into a script:
@Classic298 commented on GitHub (Sep 23, 2026):
Thanks for the clean repro. The docs example was missing a field: the completion request needs
user_message, the user message object you created in step 1. Without it the backend saves the assistant reply with no parent, so after a reload the UI can't find your message anymore.Add this to the step 2 request and it works:
Docs are updated. For future changes: send a message in the web UI with the browser dev tools open and look at the
/api/chat/completionsrequest in the Network tab. That body is exactly what the UI sends, so it's always the current reference.@vrzh commented on GitHub (Sep 23, 2026):
Thank you, works like a charm!
I initially did look at the dev tools, but saw only a request to
completions(i.e. no step 1 request):This got me confused, I thought it did not apply. But now I know!