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

Agetor

A local kanban control plane for parallel Claude Code and Codex tasks, isolated worktrees, structured approvals, and review.

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

At a glance

macOS developers coordinating several local tasks or accounts across repositories while keeping each task on its own branch and worktree.

Good choice if

macOS developers coordinating several local tasks or accounts across repositories while keeping each task on its own branch and worktree.

Check before choosing

The packaged app is Apple-silicon macOS only, Codex support is newer than the public-site copy, and the product explicitly provides no cloud relay or remote sandbox.

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

    Not eligible on current evidence

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

    The product is inactive or a required mechanism is contradicted by current evidence.

  • Shared team workspace

    Not eligible on current evidence

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

    The product is inactive or a required mechanism is contradicted by current evidence.

Harness coverage

The pinned source implements two built-in harness kinds, Claude Code and Codex, plus account or binary aliases of those same kinds. The public site still labels Codex as coming soon, so the current support record is tied to the inspected commit rather than that stale copy.

2 named integrations
  • Claude Code
  • Codex

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

    Independent harness tasks can run in parallel across repositories, worktrees, and account-specific homes.

    Source 1

  • workspace isolation

    Documented

    Git repositories use a pinned base commit and a dedicated branch and worktree per task by default.

    Source 1

  • visual review

    Documented

    The desktop board exposes task diffs in a dedicated dialog alongside run output and approval cards.

    Source 1

  • remote execution or access

    Contradicted

    The current product record says execution stays on the local machine and provides no cloud relay or remote sandbox.

    Source 1

  • shared team access

    Not established

    The current first-party record does not establish teammates entering the same live Agetor 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.

2 mapped sources
  • GitHub installers879

    stable installer downloads · 17 releases in 90 days

    Observed Open source record
  • GitHub repository26

    stars · 1 forks

    Observed Open source record

Implementation record

Inspected at commit 03b2328009b6.

  • The pinned runtime implements separate Claude Code and Codex harness kinds, including account and binary aliases.
  • Task creation and cleanup implement dedicated Git branches and worktrees.
  • The desktop client implements a structured task-diff dialog and local approval flow.
Inspected paths
  • README.md
  • src/shared/types.ts
  • src/bun/codex-tmux.ts
  • src/bun/worktree.ts
  • src/mainview/components/kanban/DiffDialog.tsx

The audit establishes implementation presence at the pinned commit, not integration reliability, usability, security, or task quality.

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

Harness integrations

1 source

Sessions, isolation and review

1 source