Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
Developer & Agent Tools

Open WebUI 0.13.4 connects local tools through Tether—with distinct sandbox boundaries

Personal model and tool connections expand, but local MCP commands run outside Tether’s workspace sandbox. The project also carries a custom branding condition.

Listen to this articleBrowser Voice
Ready
Official upstream Open WebUI interface demonstration; illustrative, not our installation.
Open WebUI official README demonstration from cdn.openwebui.com. Upstream product identification, not a recording of our installation or a test of version 0.13.4. · Official upstream organization avatar; identification only.
Event / context: 2026-11-17 UTC. Source check: Nov 20, 2026.

Open WebUI 0.13.4 expands Tether connections so a user's own model servers, tool integrations and terminals can appear in a remote Open WebUI session. The November 17 release also documents a critical distinction: sandboxing an Open Terminal workspace does not sandbox every local MCP command launched through Tether.

The official release notes describe personal connections to Ollama, LM Studio and OpenAI-compatible servers, alongside OpenAPI, MCP and terminal integrations. These features depend on the corresponding Tether and terminal versions and configuration. They do not mean every existing deployment automatically gains access to a local computer.

Two execution paths, two permission questions

For supported macOS and Windows devices, the release describes a Tether terminal sandbox limited to a selected folder, with network access disabled unless enabled and no incoming connections. It says the terminal stays stopped if enforcement is unavailable. Those are documented behaviors, not controls we have independently tested.

The same release explicitly says local stdio MCP commands run with the user's account access outside that workspace sandbox. A reader should therefore review both where an agent's terminal operates and how each tool server starts. A folder-limited terminal is not evidence that an unrelated local process has the same restriction.

Tether 0.1.14 or later is specified for personal model connectivity, with 0.1.16 required for MCP support. Tool-server configuration remains relevant too. Connecting an installed coding agent also requires that agent and its authentication; a menu entry does not provide a model subscription or a new local inference engine.

Read the license rather than the repository label

The versioned license includes a branding restriction with stated exceptions, including a user-count exception, permission and enterprise arrangements. We describe this as a custom source-available license, rather than treating the current package as unconditionally MIT or BSD. Earlier components and separate dependencies may retain their own terms.

Our analysis: the useful architectural idea is bringing personal resources into a shared interface without confusing availability with authorization. The interface should make it clear which computer executes a request, which account owns it and which isolation mechanism applies. Those questions become more consequential as a chat can invoke a terminal or a tool rather than simply return text.

For administrators, the practical next step is to inspect the exact versions and permitted tools in an existing deployment before enabling the new paths. We did not install Tether, connect a private endpoint or validate its privacy claims. Our Open WebUI repository profile provides the upstream source and licensing context for review.

EXPLORE THE SOURCE

GitHub repositories

Original source-reviewed reporting and clearly identified editorial analysis. No independent model evaluation, installation, scan or cloud deployment was performed.

Follow your curiosity.

Pass the signal.