Scenario 15: Apply a layer to a subset of target platforms
Use this when a repo opts into some harnesses but not others. For example, a backend repo that supports Claude Code and Codex but never used Cursor.
Frequency: Common · Status: Shipped
Use this when a repo opts into some harnesses but not others. For example, a backend repo that supports Claude Code and Codex but never used Cursor.
Typical commands:
harnesstap layer apply my-setup --project . --harness claude-code,codex --dry-run
harnesstap layer apply my-setup --project . --harness claude-code,codexThe --harness flag also lets you migrate one harness at a time: apply only
the new target first, verify the result, then add the remaining harnesses on
a follow-up run.
Scenario 14: Curate and clean up the local resource DB
Use this when months of scans have left the local DB with duplicates, stale resources from deleted repos, or noisy imports you no longer need.
Scenario 16: Enforce layer and plugin state in CI
Use this when you want CI to fail if the project drifts away from its layer or its pinned plugin versions.