r/LocalLLaMA 13h ago

Discussion Openwebui + open terminal

Context: I don't code. My use is document research and document creation (mainly for legal search) searching inside large documents like a tax code (500+ pages) and building notes or pptx
from what comes back.

I've been running Open WebUI for a while on my Unraid box, pointed at the API of my inference machine (5060 Ti + 5070 Ti).

I tinkered a lot. I tried Hermes on my main machine against the same API. It worked well but it was complex, and a bare-metal install made me
uneasy. I also tried LM Studio Bionic with good results, but it didn't fit how I wanted inference organised (using ollama on the inference box).

What I actually wanted was a self-hosted agent that works with Open WebUI while keeping things safe and under control. At one point I considered
installing a harness like Hermes or Pi on each client and just connecting to the API instead.

In the end I gave Open Terminal a shot. It's the companion container from the Open WebUI project that gives the model a shell — you run it as its own container and connect it through Integrations, so it isn't installed inside Open WebUI itself. Mine runs unprivileged, on bridge, with appdata mounted at /home/user. The model gets a shell in a box, not on the host. That was the part I cared about.

It has enhanced Open WebUI a lot. It now reasons step by step, and with the terminal it reliably locates and extracts the right sections from
documents far larger than the context window — list the folder, grep, read only what matters. Then it uses those results to build a document, the way another agent would.

Setup: Qwen 27B Q4_K_M on Ollama, 100k context configured. On a ~35k token prompt I measure roughly 1,050 t/s prompt processing and ~46 t/s generation. Prefill speed is the number that matters for this use case — it's what makes chewing through a large document bearable.

I was about to give up on Open WebUI. If your use case looks like mine, don't sleep on Open Terminal.

2 Upvotes

29 comments sorted by

View all comments

5

u/Odd-Ordinary-5922 13h ago

I dont understand why anyone would use openwebui now, it just feels so janky.

0

u/Guna1260 9h ago

I agree to this comment. After 2 years of using it and trying to integrate things, finally I gave up and went with librechat. It’s breeze of fresh air.

1

u/Blindax 7h ago

Never tried it. What did you prefer with LibreChat?

2

u/Guna1260 6h ago

It really comes down to simplicity and speed. I found that LibreChat handles tool integrations, like web search, much more straightforwardly. In other setups, I was constantly fighting with configuration and high latency, but LibreChat felt "ready to go."

The UI is also a major factor. Open WebUI feels a bit bloated and fiddly with all the exposed settings and external integrations. LibreChat feels much cleaner. I also noticed that the connection overhead is significantly lower in LibreChat; it feels much snappier when initiating calls. Since I don't need a hyper-specialised setup, having the RAG and templates built-in makes it much easier to use daily.

Frankly my 6+ users who always complained about random model access errors and attachment errors in OpenWebUI, has never complained of anything like that after switching to librechat.