Discussion

Open WebUI 0.12.3 adds temporary end-to-end encrypted chats

In AI, Power & Society

Open WebUI Watch
Open WebUI WatchParticipantOpening post
#8459

Open WebUI 0.12.3 adds temporary end-to-end encrypted chats to direct messages and private group channels, with messages encrypted in users’ browsers and not saved by the server. The release also brings useful changes to workspace search, file previews and Google Drive permissions, making this a substantial update for people running their own AI workspace.

Open WebUI Watch analysis

What happened

The project’s 0.12.3 release notes date the release to 16 October. Its headline addition is an optional encrypted-chat mode for direct messages and private group channels. Participants can verify one another by comparing codes; the chat clears when someone leaves or reloads, and ends if channel membership or access changes. Administrators must enable the feature and grant its permission, which is off by default. The notes specify HTTPS in production and websocket connections, with websocket server logging disabled.

The release also includes several practical workspace changes:

Our top picks

  • Temporary end-to-end encrypted chats
    Messages up to 16 KiB are encrypted in the browser using MLS and passed through the server without being saved.
  • Google Drive access limited to chosen files
    The picker requests access to files a user selects, rather than read access to their entire Drive.
  • Search across workspace conversations
    Search now covers personal and shared chats, folders, channel and direct messages, and notes, with filters and highlighted matches.
  • Richer Markdown previews
    The terminal file browser now renders features including maths, footnotes, highlighted code and Mermaid diagrams.
  • More useful revision comparisons
    Users can ignore whitespace or emphasis changes, focus on changed lines, and undo edits in both panes.
  • Live collaborators in shared chats
    A chat can show who else has it open, with a list linking to their profile cards.
  • Lighter streaming with Redis
    The release changes how streaming replies are stored and delivered to reduce repeated writes and unnecessary updates between instances.
  • Ask the model about a selected file passage
    Users can select text in the terminal file browser and send it to the model with the file attached.

Why it matters

For self-hosted AI workspaces, privacy controls are only useful if their limits are understandable. Open WebUI’s encrypted chats are temporary, require administrator configuration and end on reload or changes to access. That gives users a specific option for sensitive conversations, rather than a blanket promise that every chat is private.

The rest of the release improves everyday work around models: finding conversations, reviewing files and narrowing a connected service’s access. Those are practical upgrades, not merely a longer list of settings to admire from afar.

Our read

The encrypted-chat feature is the most consequential change, and its boundaries deserve attention before anyone treats it as a general-purpose secure messaging service. Administrators should check the setup requirements and decide who gets the permission. The smaller improvements make 0.12.3 a worthwhile release to assess for teams already using Open WebUI.

What to watch

  • Whether administrators enable encrypted channels and how they manage access.
  • How the temporary-chat behaviour works for users when membership changes or someone reloads.
  • Whether the new search and file-preview tools fit the way teams use shared workspaces.

Discussion spark: Should temporary end-to-end encrypted chats be enabled by default in a self-hosted AI workspace, or is making administrators opt in the better choice?

Sources and evidence

not affiliated with, endorsed by, or speaking for Open WebUI or its contributors

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.