Open WebUI Marks New Chat Tool Selection Loss Issue Complete, Patch Adds Request-Level Regression Tests

Open WebUI’s tool state fix has advanced: issue #32084 was marked complete on October 12. Previously, contributors reproduced tools and web search options disappearing after switching conversations in a new chat, as well as skill selections being lost after reloading. As a result, the next message could be sent without capabilities that had been enabled. Issue report

Reports covered v0.11.4 and the development branch. A typical sequence was to start a conversation from the home page, enable tools and send the first message, then switch to another conversation and return. Reporters traced the cause to the browser draft: when the first message is sent, the conversation ID is not yet available, so the options are written to a storage key without an ID; on return, however, they are looked up by conversation ID. Model defaults may re-enable some features, masking the loss of the user’s selection. Reproduction and code analysis

The public patch adds saveDraft to two flows that obtain a conversation ID, immediately saving the current draft and options under that ID. The change uses the existing draft mechanism; engineers still need to confirm whether the relevant change is included in their deployed version. Patch diff

The verification approach is also instructive. The official organization’s test repository adds two browser regression cases: one switches conversations and the other reloads the page, then each checks whether the tools list in the subsequent model request still contains the selected functions. The test description says the cases fail on the specified older development version and pass with the patch applied. This verifies the capabilities the model actually receives more directly than merely checking that the interface toggle is on. Regression tests

Official documentation says global tools must still be enabled individually in a conversation, and skill selections should be sent with each message. Therefore, a failure to preserve state could change the search or action workflows available to an agent; this is a technical inference based on the feature contract. Tools documentation, Skills documentation

The issue being closed does not mean that all stable deployments have been fixed. A separate timing variant involving quickly switching conversations after sending a message is not covered by the patch, according to its author, and the reporter also clarified the reproduction steps. Deployment teams should next check their version and verify state preservation by inspecting the actual request’s tool list. Discussion of patch scope