About

A directory you can check.

ohmyharness lists the runtimes that run coding agents and the apps that orchestrate them. It is open source, community maintained, and built so that every claim can be traced to a source.

What this is

There are dozens of AI coding tools now, and the categories are easy to mix up. A harness is the runtime that talks to a model and runs tools. An orchestrator is an app that runs one or more harnesses. A cloud agent works in a hosted sandbox and hands back a pull request. An add-on is a plugin or distribution that extends one harness or orchestrator.

Each tool has one page with the facts that matter when you choose: who makes it, what it runs on, how you pay for it, and which features are confirmed. The same facts power the comparison matrix and the tier-list maker.

How to read a tool page

Features have three states, and the third one is the important one:

✓ Confirmed✗ Confirmed absent? Not verified yet

? means nobody has checked yet. It is not a polite way of saying no. We write ✗ only when a source confirms a feature is missing, and every page lists the sources used for that entry.

Pricing and platform facts change often. Each entry carries a last verified date, and GitHub star counts carry their own check date.

Neutrality

Taglines describe what a tool does, not how good it is. Directory order is alphabetical, tier lists belong to the people who make them, and comparisons show the same rows for every tool so the format cannot favour one entry.

Facts carry sources. If a claim cannot be checked yet it stays unknown, and every page lists the sources used for that entry.

Who makes this

ohmyharness is maintained by gulivan and contributors. The code and the data are MIT licensed. Corrections from tool makers and users are equally welcome.

Data and reuse

The full dataset is published as JSON at /api/tools.json. Agents and scripts can start from /llms.txt. Reuse it under the MIT licence; a link back is appreciated.

Logos and product names belong to their respective owners and are used to identify the products.

Credits

The hero animation, logo marquee, 404 glitch, heading reveals, button sparks and tier-list confetti use components from React Bits by David Haz, MIT licensed with a Commons Clause (the components are not resold), copied into this repository. Their licence notice is kept with the component sources.

Add a tool3 steps
01

Check the facts

Find a source for each field: the tool's site, docs or repository. If you cannot confirm something, leave it null.

02

Add one file

Copy an existing entry in data/tools/ to <slug>.json and fill it in. The slug must match the filename.

03

Open a pull request

Checks validate every field. A maintainer reviews the sources, then the tool appears on the site.

Take part

57 tools are listed today. The repo also has the schema, the site code and the test fixtures.

Open data