Scenario 36: Switch global profile presets

Frequency: Common · Status: Shipped

← Back to scenarios index

Use this when you maintain separate agent setups for work, personal, or client contexts and want one command to apply the right stack to your machine home harness files (~/.claude/, ~/.codex/, …).

Typical commands:

harnesstap init
harnesstap profile list
harnesstap profile use "global default" --dry-run
harnesstap profile use work --harness claude-code,cursor
harnesstap profile status
ht work

What this gives you:

• a global default profile plugin seeded at init (tagged profile) plus ~/.harnesstap/active-profile.json pointing at it
• profile use merges the profile plugin and transitive plugin refs, then writes global harness files (not project directories)
• root shorthand ht <name> when <name> is a profile plugin and not a reserved command (ht default still resolves to global default)

init sets the active profile pointer only — it does not run global apply. Run profile use "global default" (or ht default) after bootstrap to materialize home harness files.

Create additional profiles with profile create <name> (promotes an existing plugin when the name already exists). Remove them with profile delete <name>. Combine stack plugins with plugin edit before switching.

For project-specific baselines, use apply instead (see Scenario 7 and Scenario 25).