gitwtfhub

wtf is terminals?

open-webui/terminals — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2026-04-27

★ 84PythonAudience · ops devopsComplexity · 4/5MaintainedSetup · hard

TL;DR

Terminals gives every Open WebUI user their own private, isolated container that spins up on login and tears down when they leave, so teams can share compute without users interfering with each other.

Mindmap

mindmap
  root((terminals))
    What it does
      Isolates each user
      Auto spins up and tears down
      Enforces resource limits
    Use Cases
      Shared data science infra
      Educational sandboxes
      Developer team environments
    Audience
      Platform owners
      Teams running Open WebUI
    Tech Stack
      Python
      Docker
      Kubernetes

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Give each user logging into Open WebUI their own isolated container with separate files and resource limits.

REASON 2

Set up a data-science policy with extra processing power and pre-installed Python packages for one group of users.

REASON 3

Set up a restricted sandbox policy with limited network access and storage for a different group of users.

REASON 4

Let students in an educational setting each get their own workspace without interfering with one another's runaway processes.

What's in the stack?

PythonDockerKubernetes

How it stacks up

open-webui/terminalsliuboyu/hyperledger-fabric-docs-zh_cnvideo-db/skills
Stars848484
LanguagePythonPythonPython
Last pushed2026-04-272018-01-10—
MaintenanceMaintainedDormant—
Setup difficultyhardeasymoderate
Complexity4/51/53/5
Audienceops devopsgeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1day+

Requires an Open WebUI Enterprise License for production use, plus Docker or Kubernetes infrastructure already running.

Requires an Open WebUI Enterprise License for production use, no other license terms were stated in the explanation.

Yoink these prompts

Prompt 1
I'm running Open WebUI for a team and want each user to get an isolated container. Explain how Terminals creates and tears down those containers automatically.
Prompt 2
Help me define a 'data-science' policy in Terminals with extra CPU and specific Python packages, separate from a restricted 'sandbox' policy.
Prompt 3
Explain how Terminals acts as the middleman between Open WebUI and Docker or Kubernetes when a user opens a terminal.
Prompt 4
I want to run Terminals in production. Walk me through what an Open WebUI Enterprise License is needed for and what changes between development and production setup.

Frequently asked questions

wtf is terminals?

Terminals gives every Open WebUI user their own private, isolated container that spins up on login and tears down when they leave, so teams can share compute without users interfering with each other.

What language is terminals written in?

Mainly Python. The stack also includes Python, Docker, Kubernetes.

Is terminals actively maintained?

Maintained — commit in last 6 months (last push 2026-04-27).

What license does terminals use?

Requires an Open WebUI Enterprise License for production use, no other license terms were stated in the explanation.

How hard is terminals to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is terminals for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.

Other repos in this lane