GitHub Repo
Open WebUI v0.13.0 Launches Shared Browser and Desktop Controls in Agent Workspace
Released November 3, Open WebUI v0.13.0 adds browser and desktop tabs that users can operate alongside models, and integrates file, terminal, and Git workflows. These capabilities require a compatible Open Terminal; this release also includes a database schema change, so rolling upgrades are unsupported in multi-instance deployments.
Open WebUI released v0.13.0 on November 3, expanding the workspace beside chat into a tabbed interface for multiple terminals, files, previews, and desktop sessions. The technical focus of this update is letting users observe models as they work in the same environment and take over directly when needed, rather than only receiving text results from tools. Release announcement
The new Browser tab can open websites and local development servers, with support for multiple tabs and mobile device windows. With a compatible Open Terminal, Chrome mode lets models and users share a browser session to interact with forms, navigate websites, and test generated web pages. The Desktop tab provides mouse, keyboard, clipboard, and audio features where the environment supports them. Both depend on capabilities on the terminal side; browser tools also require Chrome to be available. Upgrading the chat interface alone does not guarantee that all features will be enabled. Features and prerequisites
The official documentation describes Open WebUI as the control layer for managing models, conversations, permissions, and tools, while Open Terminal handles execution of files, commands, packages, and servers. It can run in isolation in Docker or access the host directly. A model must be able to repeatedly select tools, read their output, and correct errors; support for function calling alone does not guarantee task success. For engineering teams, the value of a shared operating view is a shorter path to inspecting artifacts and stepping in manually. This is an inference about the workflow, not a measured improvement in success rates. Open Terminal architecture
There are also clear deployment constraints. This release includes a database schema migration, and the official guidance requires coordinated updates across multi-worker, multi-server, and load-balanced environments; mixing old and new versions may cause failures. The upgrade guide further says to stop all replicas, let a single instance complete the migration, and then start the remaining instances on the new version. Reverting only the container image will not undo database changes. Engineers should next validate terminal compatibility, model performance with tool operations, and whether existing plugins pass staging tests before scheduling the production rollout. Upgrade and migration guide