HarnessMatch

Search 67 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

HAPI

A local-first web, PWA, and Telegram control surface for handing off five coding-agent CLIs between terminal and remote devices.

Status
Active
License
AGPL-3.0
Source access
Open source
Record checked
Open product siteInspect sources

At a glance

Developers who want to keep agent execution on their workstation while checking sessions, approvals, files, diffs, and terminals from a browser or phone.

Good choice if

Developers who want to keep agent execution on their workstation while checking sessions, approvals, files, diffs, and terminals from a browser or phone.

Check before choosing

The GUI is browser-based, current sources do not establish automatic worktree isolation, and multi-user shared-workspace behavior is not documented.

Workflow fit

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

  • One agent + review

    Good fit

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

    Every required mechanism is documented; current sources do not establish the preferred workspace isolation mechanism.

  • Parallel local tasks

    Conditional fit

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

    The product may fit, but current sources do not establish workspace isolation.

  • 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

HAPI wraps five named local agent CLIs. Each CLI keeps its own runtime, authentication, history, tools, and provider behavior.

5 named integrations
  • Claude Code
  • Codex
  • Cursor Agent
  • Grok Build
  • OpenCode

Workflow mechanisms

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

3 of 5 documented

  • parallel sessions

    Documented

    The web client groups and tracks independent live sessions across projects and connected machines.

    Source 1

  • workspace isolation

    Not established

    Scoped workspace roots limit browsing and session start directories, but current sources do not establish automatic branch or worktree isolation.

  • visual review

    Documented

    The web client renders file changes in an expandable visual diff with line counts and additions and deletions.

    Source 1

  • remote execution or access

    Documented

    Web, PWA, and Telegram clients can control the named agents and terminal on the working machine through relay or self-hosted access.

    Source 1

  • shared team access

    Not established

    Current first-party sources do not establish teammates entering the same live HAPI workspace.

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 9d07857570bb.

  • The shared flavor registry implements five named coding-agent CLI integrations.
  • The web client groups live sessions by project and machine and implements structured visual diffs.
  • The hub implements the browser-facing control surface used for relay and self-hosted access.
Inspected paths
  • README.md
  • shared/src/flavors.ts
  • web/src/components/SessionList.tsx
  • web/src/components/DiffView.tsx
  • hub/src/web/server.ts

Session grouping is evidence of concurrent-session control, not automatic worktree isolation or shared human-team workspaces.

First-party evidence

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

3 first-party sourcesGUI record checked

Product and workflow

1 source

Sessions, isolation and review

2 sources
View 1 more source