HarnessMatch

Search 73 product records by name, workflow, interface, or documented capability.

Quick access
Use ↑ ↓ to move, Enter to open, Esc to close.

Quick access links shown.

Menu
← GUI catalog

Multi-harness workspace

webmux

A self-hosted browser dashboard that owns worktrees, tmux layouts, agent events, services, and optional containers.

Status
Active
License
MIT
Source access
Open source
Record checked
Open product siteInspect sources

At a glance

Developers who want a hackable web control plane on their own machine or server, including mobile check-ins.

Good choice if

Developers who want a hackable web control plane on their own machine or server, including mobile check-ins.

Check before choosing

Deployment and secure network exposure are the user's responsibility, and full in-app chat features are limited for custom agents.

Workflow fit

Existing evidence gates classify four predefined workflows. Bands are non-numeric and do not rank product quality.

  • One agent + review

    Strong fit

    Stay close to one coding session and inspect changes in a dedicated visual surface.

    Current sources document visual review, workspace isolation.

  • Parallel local tasks

    Strong fit

    Run several coding tasks on one machine without their branches or files colliding.

    Current sources document parallel sessions, workspace isolation, visual review.

  • Remote control

    Good fit

    Start or revisit coding work away from the machine where the repository is running.

    Every required mechanism is documented; current sources do not establish the preferred shared team access mechanism.

  • Shared team workspace

    Conditional fit

    Let teammates enter the same live workspace to watch, steer, preview, or review work.

    The product may fit, but current sources do not establish shared team access.

Harness coverage

Codex and Claude Code receive full in-app chat, history, interrupt, and resume controls. Custom CLIs are terminal-first and can optionally define a resume command.

Custom CLI accepted
  • Codex
  • Claude Code

Workflow mechanisms

Unknown means the current first-party record does not establish the mechanism; it is not converted into evidence of absence.

4 of 5 documented

  • parallel sessions

    Documented

    One dashboard manages parallel worktree and tmux agent sessions.

    Source 1Source 2

  • workspace isolation

    Documented

    The service creates Git worktrees and can add Docker sandbox isolation.

    Source 1Source 2

  • visual review

    Documented

    The dashboard surfaces PRs, CI checks, comments, services, and session state.

    Source 1Source 2

  • remote execution or access

    Documented

    A browser and mobile-oriented chat UI reconnect to persistent host sessions.

    Source 1Source 2

  • shared team access

    Not established

    The current official record does not establish multi-user access controls or shared steering.

Official webmux product demo from the same source commit used for the implementation audit.
Official product media
webmux preview

Technical and public context

Implementation inspection and source-native activity provide investigation context. Neither changes workflow fit.

Inspect implementation record and public activityContext, not workflow fit

Public activity signals

Daily source snapshots provide ecosystem context only. They do not affect workflow fit or capability claims.

1 mapped source

Implementation record

Inspected at commit 99cb139eac4b.

  • The backend owns worktree and tmux session lifecycle with rollback behavior.
  • Codex and Claude have first-class chat, interrupt, history, and resume capabilities.
  • Custom agents are command-configurable but terminal-first, without the same built-in chat, history, and interrupt integration.
  • The browser and mobile-oriented views derive their state from managed worktree sessions.
Inspected paths
  • backend/src/services/worktree-service.ts
  • backend/src/services/agent-registry.ts
  • backend/src/services/agents-ui-service.ts
  • backend/src/adapters/agent-runtime.ts

The audit does not establish secure internet exposure; the documented deployment remains a service on infrastructure the user controls.

First-party evidence

Sources establish specific current GUI claims; their count does not add fit points.

4 first-party sourcesGUI record checked

Product and workflow

1 source

Harness integrations

1 source

Sessions, isolation and review

1 source

Public code and implementation

1 source