DumbWareio

DumbTerm: Access a Linux Terminal in Your Browser

DumbTerm provides browser-based access to a terminal running locally or in a Docker container. It suits self-hosters and developers who need a convenient terminal interface, with optional PIN protection and Starship prompt integration.

View on GitHub Compare
Stars
247
Forks
11
Stars, last 30 days
-2

Our take

Health score

20/100

How it is scored
Activity
19
Community
20
Issues
21
Pull requests
20

-2 stars in the last 30 days

  • Fewer contributors than 86% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

246

Forks

12

Change since Nov 14, 2026: 0 stars·0 forks

Overview

DumbTerm is a web application that connects a browser-based terminal interface to a shell process, using XTerm.js and WebSockets. It can run against the host environment or in a Debian-based Docker container, making command-line access available from desktop and mobile browsers.

It is a practical fit for self-hosters and developers who want a lightweight web terminal for a sandbox, a remote access setup behind an authentication proxy, or a demonstration environment. It is not a substitute for a hardened access-control layer when exposing a shell to untrusted networks.

Key Features

  • Browser terminal with real-time input and output over WebSockets.
  • Docker image with common command-line utilities and optional Starship prompt integration.
  • Optional numeric PIN protection, failed-attempt lockout, and session expiration.
  • Multiple terminal tabs with reordering, renaming, shortcuts, and persisted terminal history.
  • Terminal search, clickable links, and responsive desktop and mobile interface.
  • Configurable data and settings directories through Docker volume mounts.
  • Demo mode for a simulated terminal experience.

Use Cases

  • Developers can run scripts or test command-line tools in an isolated Docker environment without installing those tools on their workstation.
  • Self-hosters can reach a server shell from a browser, especially when placing the service behind HTTPS and an authentication provider.
  • Teams can create a browser-accessible terminal for tutorials, demos, or showcasing command-line examples using demo mode or a configured environment.
  • Administrators can use a browser as an alternative terminal client when they want access from multiple device types.

Getting Started

The recommended setup is Docker Compose. A minimal service can use the published image:

services:
  dumbterm:
    image: dumbwareio/dumbterm:latest
    ports:
      - "3000:3000"
    volumes:
      - ./config:/root/.config
      - ./data:/root/data
    environment:
      DUMBTERM_PIN: "1234"

Start it with docker compose up -d, then open http://localhost:3000. Set a strong PIN or use an external authentication provider before making the service accessible beyond a trusted network. See the README for configuration and local development instructions.

Alternatives

  • tabby-web: Tabby Web serves the Tabby terminal and syncs client configuration, while DumbTerm provides a simpler browser interface to local or Docker terminals.
  • sshx: sshx focuses on sharing a live terminal with collaborators through encrypted links, while DumbTerm provides persistent browser access to local or Docker terminals.
  • jumpserver: JumpServer manages privileged access across servers and other infrastructure, while DumbTerm focuses on browser access to local or Docker terminals.
ProjectLanguageLicenseStarsStatus
DumbTermJavaScriptGPL-3.0247Not checked yet
tabby-webPythonMIT1.5kQuiet
sshxRustMIT7.7kMaintained
jumpserverPythonGPL-3.031.7kActive

Considerations

  • A web terminal grants shell access to the environment where it runs. The project recommends HTTPS, origin restrictions, a strong PIN, and an authentication provider for deployments that are reachable outside a trusted network.
  • Docker is the recommended deployment path. Local development requires Node.js 20 or later according to the README, and node-pty may need additional setup on Windows.
  • Starship is enabled by default in the Docker image; local use requires Starship to be installed separately if it is wanted.
  • The repository is not archived. The README describes the container as Debian Trixie-based for versions 1.2.1 and later.

Found this useful?

Share it with someone who would like DumbTerm.

Comparisons