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

OpenHands Agent Canvas

A visual OpenHands workspace for parallel agents, per-conversation worktrees, diffs, local or remote backends, automations, and ACP harnesses.

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

At a glance

Teams or individuals who want one open interface across OpenHands and three external harnesses, with self-hosted or managed execution backends.

Good choice if

Teams or individuals who want one open interface across OpenHands and three external harnesses, with self-hosted or managed execution backends.

Check before choosing

The pinned testing matrix does not yet cover real external-harness credentials, subscription-login paths, macOS, or Windows in CI, so integration presence is not reliability evidence.

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

    Strong fit

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

    Current sources document remote execution or access, shared team access.

  • Shared team workspace

    Strong fit

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

    Current sources document remote execution or access, shared team access, workspace isolation, visual review.

Harness coverage

Four providers are documented directly, and a custom stdio ACP server can be configured. The external harness keeps its own model, tools, execution, and credentials; ACP compatibility is not arbitrary-CLI support.

4 named integrations
  • Claude Code
  • Codex
  • Gemini CLI
  • OpenHands

Workflow mechanisms

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

5 of 5 documented

  • parallel sessions

    Documented

    Agent Canvas runs multiple agents simultaneously and keeps their conversations visible in one interface.

    Source 1

  • workspace isolation

    Documented

    The product page documents a separate Git worktree for each parallel agent.

    Source 1

  • visual review

    Documented

    The current client implements a dedicated Changes route that loads and renders repository diffs for the active conversation.

    Source 1

  • remote execution or access

    Documented

    The same frontend switches among local agent servers, self-hosted remote VMs, and OpenHands Cloud backends.

    Source 1

  • shared team access

    Documented

    Official sources describe team-shared Agent Server access and team sharing through the managed cloud backend.

    Source 1

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.

2 mapped sources
  • GitHub installers511

    stable installer downloads · 4 releases in 90 days

    Observed Open source record
  • GitHub repository82,905

    stars · 10,680 forks

    Observed Open source record

Implementation record

Inspected at commit 1708efc44608.

  • The current Agent Canvas repository documents OpenHands, Claude Code, Codex, Gemini CLI, and custom stdio ACP configuration.
  • The client implements a dedicated repository-changes route backed by a unified Git-diff query.
  • The testing matrix records current credential, subscription-login, and platform coverage gaps for ACP providers.
Inspected paths
  • README.md
  • docs/ACP_AGENTS.md
  • docs/TESTING_MATRIX.md
  • src/routes/changes-tab.tsx
  • src/hooks/query/use-unified-git-diff.ts

The audit establishes integration and review mechanisms at the pinned commit; its own test matrix prevents treating presence as cross-provider reliability evidence.

First-party evidence

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

5 first-party sourcesGUI record checked

Product and workflow

1 source

Harness integrations

2 sources
View 1 more source

Sessions, isolation and review

1 source

Public code and implementation

1 source