Open WebUI released version 0.10.0 on 29 June 2026, adding shared folders and a system-wide event layer to its model-chat workspace. The release makes a more consequential pitch: one workspace where teams can share conversations, automate responses to system activity and connect agent sessions to a computer.
Open WebUI Watch analysis
What happened
Folder owners can share a folder and the chats beneath it with named users or groups, granting read or write access. Recipients see it in their sidebar; someone else's chat opens read-only; nested folders inherit access; and there is no public sharing link. An administrator must enable the sharing permission, which is off by default. Automatic compaction for long chats is also available but off by default, while Computer agent support can give chat sessions access to files, a terminal, git and the web on a user's own machine.
The other hinge is events. New Event Functions can run custom Python when signups, chat deletion, model creation, startup or configuration changes occur, while filtered webhooks can send selected events to external endpoints or chat destinations. The documentation lists more than 170 event names, but makes the reliability boundary explicit: handlers are fire-and-forget, failed runs are not retried, and there is no exactly-once guarantee or coordination across replicas.
Why it matters
Together, these features turn an individual chat front end into a collaborative operating surface. Shared folders give teams common context without requiring public links, and events provide hooks for provisioning, audit logs and alerts. That also widens the blast radius of configuration mistakes: folder permissions, custom code, webhooks and computer access now deserve the same deliberate review as any other privileged automation. The release makes native tool calling the default and includes database migrations that cannot be downgraded, so backup and compatibility testing are part of the upgrade rather than optional garnish.
Our read
Open WebUI has not merely added another drawer to the cabinet; it has handed the cabinet a keyring and wired it to the bell. That is genuinely useful. It is also how a tidy chat tool becomes an operational system, complete with the traditional operational-system hobby of waking every replica to ring the same bell.
What to watch
- Whether shared-folder inheritance stays understandable as team structures become more complex.
- How administrators make Event Functions idempotent across retries, restarts and multiple replicas.
- Whether automatic compaction preserves decisions and nuance in genuinely long working conversations.
- Whether default native tool calling surprises older models or established workflows after upgrading.
Discussion spark: At what point does a shared chat workspace become operational infrastructure, and which guardrail would you require first: permission reviews, event idempotency, isolated computer access or rollback-tested upgrades?
Sources and evidence
- Open WebUI v0.10.0 release notes (29 June 2026, 19:17 UTC)
- Open WebUI v0.10.0 release API record (29 June 2026, 19:17 UTC)
- Event Function (30 August 2026, 18:43 UTC)
- Folders and Projects (30 August 2026, 18:43 UTC)
not affiliated with, endorsed by, or speaking for Open WebUI or its contributors