Open Terminal

Open Terminal is a lightweight, self-hosted terminal that gives AI agents and automation tools a dedicated environment to run commands, manage files, and…

  • AI
  • Development
Open Terminal is a lightweight, self-hosted terminal that gives AI agents and automation tools a dedicated environment to run commands, manage files, and execute code all through a simple API.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 5 days ago
Popular
713,591 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 12 days ago

GitHub stars
3,591
Open issues
91
Last commit
2026-11-16
Latest release
v0.17.20
License
MIT
Activity
rising

Checked 5 days ago - source: GitHub (open-webui/open-terminal)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Protect it with an API key When you start the server, pass a strong --api-key, especially if you use --host 0.0.0.0 so it listens on all your network addresses. That key is what clients present to access the terminal, and without a real one the app may be exposed to anyone who can reach your machine. source
  • Expose port 8000 in Docker When running the container, keep -p 8000:8000 in your Docker command. Port 8000 is the address your browser, Open WebUI, or MCP client uses to reach the app, and without that mapping you may see the container running but still not be able to connect. source
  • Keep your config file safe Your TOML config holds settings like api_key, host, port, and log_dir, and environment variables can override them. Keep a backup and understand what it points to, because losing it means you may have to re-create your access key, storage paths, and server settings from scratch. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which directory should I mount in Docker for Open Terminal files?

Map a Docker volume to /home/user, as in the documented open-terminal:/home/user mount.

Why is Open Terminal unreachable even though the container is running?

You need to expose port 8000 with -p 8000:8000. Port 8000 is the address used by the browser, Open WebUI, or MCP client to reach the app.

What happens if I don't set an API key for Docker?

A key is generated automatically. You can retrieve it with docker logs open-terminal.

What should I back up so I don't have to recreate Open Terminal settings?

Back up the TOML config file, because it holds settings such as api_key, host, port, and log_dir. Losing it may require recreating your access key, storage paths, and server settings.

Can I install additional packages at runtime in the slim or alpine images?

No; slim and alpine do not support OPEN_TERMINAL_PACKAGES, OPEN_TERMINAL_PIP_PACKAGES, or OPEN_TERMINAL_NPM_PACKAGES. To add packages, extend the Dockerfile for those variants.

Answers sourced from github.com, github.com, github.com

Community

Collected 48 days ago - public community threads