What are the headline features in 0.10.2?

Three: streamed reasoning display, so a model's thinking or reasoning content now appears as it is generated and renders correctly in the chat overview and in exported conversations; folder uploads to knowledge bases, so a folder you drag in or sync keeps its subfolder structure instead of being flattened into loose files; and the Memory System Context toggle, which lets an administrator keep memory tools available while choosing not to inject stored memories into the system context.

Is 0.10.2 a security release?

Yes. The release notes include a security advisory stating that the version contains security and access-control fixes and recommending that production deployments be updated at the earliest convenience. Not all of the security fixes are enumerated in the notes; some are intentionally withheld for a short time to give administrators time to upgrade. That means the security case to take the patch stands even if you do not adopt any of the new features.

A single request that returns an authorization error no longer signs you out while your session is still valid, because the app now confirms session status before redirecting to login. Web-search domain allow and block rules are now matched against the host, closing a gap where some URLs could slip past the filter. Image-generation prompts are no longer written to server logs at the default level. Upgrading an existing SQLite database no longer crashes during the user-table migration. And non-admin users can save their interface settings again, which previously failed with a server error.

Open WebUI 0.10.2: Streamed Reasoning and Security Fixes

Short answer: Open WebUI 0.10.2 is a feature-and-fix release. The headline additions are streamed reasoning display, so models that emit thinking content now show it as it streams and it renders correctly in the chat overview and exports; folder uploads to knowledge bases, so dragging or syncing a folder recreates its subfolder structure instead of flattening it; and a Memory System Context toggle, so an administrator can keep the memory tools available while choosing not to add stored memories to the system context. Around the features, the release carries a security advisory: it includes security and access-control fixes, the release notes recommend updating production deployments at your earliest convenience, and some fixes are intentionally not enumerated to give administrators time to upgrade. Other fixes include fewer unexpected logouts, a web-search domain filter that now matches the host, and safer SQLite database upgrades. For an operator, the theme is a usable feature set on top of a security patch that is worth taking on its own.

Streamed reasoning changes what a chat can show

The streamed reasoning feature is the addition most likely to be noticed, because it changes what the interface displays for models that emit a separate reasoning or thinking channel. Before 0.10.2, that content was either not shown as it streamed or did not render correctly in the chat overview or in exported conversations. In 0.10.2 it is shown as it streams and renders correctly in those other surfaces. For a deployment that runs reasoning-capable models, the practical effect is that the reasoning is visible where the user is looking, not hidden until after the fact.

The operator relevance is the rendering across surfaces, not just the live stream. A feature that streams correctly in the live view but breaks in the overview or the export is a partial feature, because the user sees different things depending on where they look. The release notes call out the overview and export specifically, which is the signal that the fix was about consistency of the reasoning display across every place the conversation appears.

Folder uploads keep structure

Folder uploads to knowledge bases previously flattened a folder into loose files, so the subfolder organization a user had on disk was lost on import. In 0.10.2, dragging a folder into a knowledge base, or syncing one, recreates the subfolder structure. For an operator who is importing an organized corpus, that is a meaningful change: the hierarchy that made the corpus navigable locally is preserved in the knowledge base, which matters for a large or structured collection where flat files are hard to find.

The change is worth verifying if you import folders, because the fix is in the import path and the observable result is the presence of the subfolders in the knowledge base after an upload. If your corpus is flat, the change is transparent. If it is nested, the difference between the old flattening behavior and the new structure-preserving behavior is exactly what you are looking for.

The security patch is the reason to upgrade

Regardless of whether you adopt the new features, the security advisory is the strongest reason to take 0.10.2. The release contains security and access-control fixes, and the release notes recommend updating production deployments at your earliest convenience. The fact that some fixes are not enumerated in the notes, withheld for a short time to allow administrators to upgrade, is a standard and reasonable practice, but it also means you cannot fully scope the security change from the release notes alone.

For a production instance, the security advisory moves this from a convenience patch to a recommended update. The honest framing is that 0.10.2 should be treated as a security patch that happens to add useful features, and the upgrade decision should be driven by the advisory, not by whether you want streamed reasoning. The feature set is the bonus; the security fix is the point.

The verification for the security side is the standard one: apply the update, confirm the instance starts cleanly, confirm that logins and shared access still work as expected, and confirm the web-search domain filter behaves as configured. The feature verification is separate: confirm streamed reasoning renders in the live view, the overview, and an export, and confirm a folder upload preserves subfolders.

The sequencing is to take the security patch first and treat the features as the reason to enjoy it. If you would take 0.10.2 for the security advisory alone, that is the complete justification; the streamed reasoning, the folder uploads, and the memory context toggle are the bonus that comes with the update. That framing keeps the upgrade honest: you are not adopting features you have not verified, you are taking a security patch and confirming, in the same window, that the new features behave the way the release notes describe.

Limitations

A release note is not a deployment audit. It does not inspect your operating system, network policy, credentials, storage, backups, or administrative process.
Version numbers and documentation change. Pin the exact artifacts you test, record the date, and re-check upstream material before a production change.
A feature that exists in a package or command does not automatically fit your threat model. Authentication, authorization, logging, patching, recovery, and abuse controls remain operator responsibilities.
This article contains no benchmark, uptime promise, adoption statistic, cost saving, or client result. Measure those claims in your environment; the release record can only describe what shipped.

Related infrastructure context

For the physical layer around a systems deployment, TismTek provides fiber and network infrastructure work near Aurora. The team also documents on-premises compute and private AI systems. For a site discussion, call (720) 694-1976. See the Open WebUI self-hosted upgrade risk checklist for recovery planning and the Open WebUI private model stack for the broader on-premises context.

Sources

Open WebUI v0.10.2 release notes — consulted September 15, 2026.
Open WebUI v0.10.1 prior release — consulted September 15, 2026.
Open WebUI documentation — consulted September 15, 2026.