Scenario 20: Inspect supported platforms before targeting
Use this when planning which harnesses to use as main and aliases, or when an unfamiliar harness ID appears in someone else's layer.
Frequency: Occasional · Status: Shipped
Use this when planning which harnesses to use as main and aliases, or when an unfamiliar harness ID appears in someone else's layer.
Typical commands:
harnesstap harness list
harnesstap harness list --supported
harnesstap harness list --format json | jq '.[] | {id, supports}'The registry is the source of truth for the harness IDs that HarnessTap understands today, and tells you which feature surfaces (instructions, skills, rules, MCP, hooks, agents, commands, …) each harness supports.
Scenario 19: Sync plugin resources from install trees
Use this when plugin install trees on disk have changed and HarnessTap's library copies are stale or missing resolved versions.
Scenario 21: Detect drift between project files and the last applied layer
harnesstap status . --check harnesstap status . --check --format json # exit 1 when drift exists