CLIScenariosScenario guides

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.

Frequency: Occasional (once after init, then when your toolchain changes) · Status: Shipped

← Back to scenarios index

Use this when you want one harness to be your canonical setup and a few others to be kept aligned with it.

Typical commands:

harnesstap harness set --main claude-code --aliases cursor,codex
harnesstap harness status

Notes:

  • harnesstap harness list is the source of truth for valid harness IDs.
  • --interactive is available, but the non-interactive flag path is the main automation-friendly workflow.

Scenario 1: Bootstrap HarnessTap on a machine and discover existing defaults

Use this when setting up HarnessTap for the first time on a laptop, dev box, or CI-like agent environment.

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...