Open WebUI’s new Terminals service can give each user, chat or model its own sandboxed computer, where AI models can run commands and edit files. For teams using Open WebUI, it replaces the awkward choice between sharing one machine and setting up computers by hand.
Open WebUI Watch analysis
What happened
The Open WebUI team says Terminals runs alongside Open WebUI and starts separate computers on demand. An administrator can configure images, CPU, memory, storage, network access and setup scripts once; users with permission can then create machines from the chat interface, with a project ready to go.
The computers run as containers on a Docker host or Kubernetes cluster, and their files stay on the organisation’s own storage. Open WebUI says Terminals 0.4.2 requires Open WebUI 0.13.4 or later. It is free for personal, non-commercial use; organisations need an Enterprise licence with Terminals access.
Why it matters
A model that can work on files and run commands needs somewhere to do it. Terminals gives teams a way to provision that working environment per person, conversation or model, while letting administrators set limits centrally. That makes it more than a new button in the chat: it is infrastructure for giving AI agents a defined workspace.
The choice of backend also has consequences. Docker offers a simpler starting point, while Kubernetes supports per-computer storage limits and network policies. The setup is not entirely hands-off: administrators still decide who can create machines, what they can access and where their files live.
Our read
The appealing idea is that a project can arrive with its own ready-to-use computer, without IT manually preparing one for every person. The useful safeguard is that the organisation, rather than each model, sets the boundaries. Teams considering a rollout should first decide who gets a separate machine, what it can reach and how much resource it can consume. “Sandboxed” is a good start, not a substitute for those decisions.
What to watch
- Whether teams find per-user or per-chat machines easier to manage than a shared computer.
- How administrators configure network access, resource limits and permissions in practice.
- Whether Open WebUI expands the service’s capabilities or changes its organisational licensing.
Discussion spark: Should AI agents get a separate computer for every user or chat, or is a shared, tightly managed environment the better default?
Sources and evidence
- Source update (18 November 2026, 03:55 UTC)
- Source update (18 November 2026, 03:55 UTC)
not affiliated with, endorsed by, or speaking for Open WebUI or its contributors