Scenario 40: Use project profile config

Frequency: Common · Status: Shipped

← Back to scenarios index

Use this when a repository ships apm.yml with named profiles so teammates can switch stacks without remembering plugin selectors.

Create the file with ht config init (from local profile plugins) or copy a team template. See Project config for the apm.yml shape.

Inspect the config

ht config show
ht config validate
ht use --list

config validate checks that inline profiles reference plugins defined in the same file and that default profile/environment keys resolve.

Switch profiles

ht use --profile dev
ht use --profile prod --dry-run
ht use                        # interactive picker when multiple profiles exist

ht use resolves the profile source (local plugin, catalog selector, or inline plugin table), applies the profile to home harness paths, and optionally switches the active environment.

For machine-wide presets outside a repo, use profile use instead (Scenario 36). For repo baselines without project config, use apply (Scenario 7).