How to configure model routing

Override Harbourmaster model tiers through GitHub Action inputs or environment variables. Harbourmaster does not read a repository model configuration file.

The Action maps inputs to HARBOURMASTER_*_MODEL variables. Defaults live in the configuration reference.

Use Action inputs

Set bedrock_model for all tiers. Set bedrock_fast_review_model, bedrock_deep_review_model, bedrock_editor_model, or bedrock_fallback_model for a specific tier. A specific tier input takes precedence over bedrock_model.

Use a provider/model-id value. See the GitHub Action reference for the input contract.

The code-quality reviewer uses GPT-5.6 Sol with low reasoning effort when the deep-review default is unchanged. A deep-review override also changes that reviewer unless you set an agent-specific TypeScript override.

Use environment variables

For direct GitHub CLI runs, set the corresponding environment variables:

export HARBOURMASTER_BEDROCK_MODEL=amazon-bedrock/harbourmaster-gpt-5-6-terra-medium
export HARBOURMASTER_DEEP_REVIEW_MODEL=amazon-bedrock/harbourmaster-gpt-5-6-luna-extra-high

This sample sets every tier to Terra, then overrides deep review to Luna. It is not the default map. The deep review tier uses Luna. The other tiers use Terra in this example.

Change bundled defaults

Change the TypeScript model configuration for per-agent rules, fallback lists, provider availability, or optional cost metadata. Keep the bundled OpenCode model aliases consistent with those defaults.

Verify the routing

Run one review after the change. Open the job log and find a reviewer_started logfmt line. Confirm model and modelTier match the intended route.

See the configuration reference for the default models and environment variables.