HarnessTap CloudOpen catalog · free on day one

Personas for your coding agent.

Compose what runs, swap how it runs, and install the same deck on Claude, Codex, and Cursor from one git repo.

Context · environment · layer · deckDeck model
Deck
Your personal ordered collection of layers—cherry-pick from org catalogs and local layers, then apply to projects with `deck apply`.
Layer
A reusable, versioned recipe you combine and apply at project or machine level—publish to a catalog or share through an export.
Profile
A layer tagged `profile`—a switchable global preset you activate with `profile use` to update machine-wide harness files.
Resource
The smallest piece of agent configuration you can mix and match—either context-side (what the agent knows) or environment-side (how it runs).
Environment
Named runtime settings you switch in one command—move between dev, staging, and production, or between customers and teams, without rebuilding your setup.

Learn the model →

One catalog for your org. Native on every harness.

HarnessTap Cloud stores your organization's catalogs of layers, resources, and decks. The CLI pulls approved releases, publishes updates, and syncs the same setup to Claude, Cursor, and Codex on each developer's machine.

The open catalog ships free on day one — browse layers, review version history, and pull any release after review.

Cloud · CLI · local harnessOne deck, every agent
HarnessTap Cloud, CLI, and local agent harnesses working togetherHarnessTap Cloud stores organization catalogs of configured layers with plugins and environments. The HarnessTap CLI pulls approved releases and syncs them to Claude, Cursor, and Codex on the developer laptop.Your laptopAgent harnessesClaudeCursorCodexHarnessTap CLI$ hd deck pullsyncing layers...✓ native on 3 harnessespull · publish · env swapHarnessTap CloudOrgacme-engineeringCatalogopen catalogDeckplatform-personasLayer · FrontendPluginskills · MCPEnvironmentstagingLayer · BackendPluginhooks · rulesEnvironmentprod

Browse layers and decks from the open catalog.

Each layer is a versioned capability with release history. Pull any release from the CLI after review.

Frontend engineer

v1.0.0

React and Next.js UI skills, impeccable design review, Playwright E2E, and Chrome DevTools MCP for component work across local, preview, and production.

Configured layers
9
Published releases
1
react
nextjs
tailwind
accessibility
playwright
profile

Browse 1 reviewed releases and configured layers in the open catalog after sign-in.

Backend engineer

v1.0.0

Feature-dev exploration, superpowers TDD, code review gates, and context7 docs for API design, debugging, and on-call response across staging and prod.

Configured layers
10
Published releases
1
api-design
postgres
on-call
tdd
code-review
profile

Browse 1 reviewed releases and configured layers in the open catalog after sign-in.

Agentic AI engineer

v1.0.0

Superpowers orchestration, ECC multi-agent OS, claude-flow swarms, skill-creator evals, and memory plugins for building reliable agent systems.

Configured layers
12
Published releases
1
multi-agent
mcp
evals
orchestration
memory
profile

Browse 1 reviewed releases and configured layers in the open catalog after sign-in.

Showing 3 of 13 configured layers from the open catalog.

How HarnessTap works

Separate what you run from how you run it, then sync the result to every harness.

What vs how

What

Context-side resources

skills, rules, MCP servers, hooks, agents, commands

How

Environment-side values

env vars, model config, permissions

Composition

plugin refs, layer refs

MCP server definitions describe what to connect to; tokens and URLs are supplied as environment values.

Three payoffs

  • Switchable configuration

    Same layer, new environment in one command

    Declare what each capability needs once. Swap prod, staging, or personal values without copying the whole setup.

  • Context curation

    Turn skills and MCP servers off when you are done

    Stack only what a task needs. Remove the loadout cleanly instead of letting context accrete.

  • Cross-harness reach

    One repo, native on Claude, Cursor, and Codex

    Claude installs from the repo. Cursor and Codex read the generated native files from the same deck.

Configure once. Switch anywhere.

Every harness ships its own plugin format. Config values freeze in settings. Context stacks up because it is easier to add than remove. HarnessTap separates what you run (context-side resources: skills, MCP, rules) from how you run it (environment-side values: secrets, models, permissions), composed into layers and cascaded into every harness.

HarnessTap CLI

hd deck use staging

Same plugins, new environment. Re-bind tokens, models, and permissions in one local command. The web app publishes decks; environment swap runs in the CLI.

A plugin anyone can install. A deck only you can reconfigure.

HarnessTap adds optional governance without blocking plain OSS installs

Without HarnessTap

  • claude plugin install works on the repo as-is
  • Other harnesses read AGENTS.md, .cursor/rules/, and similar generated files

With HarnessTap

  • CLI: swap prod and staging in one command
  • Curate context, detect drift, sync every harness from .harnesstap/deck.json

HarnessTap is pure upside. Never required to use what you publish.

Team governance

Ship layers and decks from the CLI, review releases in Cloud, and pull approved setups into every project.

Publish → Review → Govern → Pull

Read the CLI reference for pull and publish commands.

  1. 1

    Publish

    Push configured layers and decks from the CLI to your org publishedLayer.

  2. 2

    Review

    Teammates see changelog and semver before anyone pulls.

  3. 3

    Govern

    Roles, domains, and access control over what gets adopted.

  4. 4

    Pull

    Approved setup lands in the project via the CLI.

  • Catalog governance

    Curate and publish layers and decks for your org.

  • Change history teams trust

    Review releases before teammates pull updates.

  • Organization access control

    Roles, invitations, domains, and SSO path.

  • CLI-connected workflows

    Pair the HarnessTap CLI with the shared cloud organization.

Plans and signup

Free tier

Start with the open catalog today.

Up to 3 users and 1,000 API requests per day, with the full open catalog included.

Compare plans

Upgrade path

Unlock paid governance when you scale.

Scale roles, domains, and review controls as your team grows into the platform.

View pricing

Ship your first persona from the open catalog.

Sign up, then pull approved layers from the open catalog in minutes.