Scenario 3: Override harness preferences for one repository
Use this when your global preference is not the right fit for a specific repo. For example, you may usually author in Claude Code but want one project to...
Frequency: Common · Status: Shipped
Use this when your global preference is not the right fit for a specific repo. For example, you may usually author in Claude Code but want one project to use Codex as the canonical harness.
Typical commands:
harnesstap harness project set --project . --main codex --aliases claude-code,cursor
harnesstap harness project status --project .You can also set --materialization-strategy symlink-preferred or copy when
the project needs a specific write strategy. See Scenario 13 for the tradeoff.
Scenario 2: Choose a default main harness and alias harnesses
Use this when you want one harness to be your canonical setup and a few others to be kept aligned with it.
Scenario 4: Scan an existing repository and import its current harness setup
Use this when a repository already contains agent instructions, skills, MCP config, rules, hooks, or agent files that you want HarnessTap to manage.