Configure and validate the local model catalog

Start with the bundled catalog

TCalc ships with 20 model entries across seven catalog providers and configuration for nine provider endpoints, including local runtimes. The catalog records context windows, output limits, price fields, tool and image support, privacy mode, coding and latency signals, and review dates.

Missing workspace overrides are normal. The VS Code extension silently checks catalogs/models.json and .tcalc/models.json, then keeps using the bundled catalog when neither file exists. Those paths are optional customization points, not installation requirements.

Add a workspace override

1. Copy the bundled catalog shape into catalogs/models.json or .tcalc/models.json in the workspace.
2. Keep every required field typed correctly and use ISO dates for updatedAt.
3. Validate the file before scanning with it.
4. Run TCalc: Update Model Catalog in VS Code to see the bundled and override status.

pnpm cli catalog validate .tcalc/models.json
pnpm cli recommend . --catalog .tcalc/models.json --goal refactor

Why a scan may show only one fitting model

Recommendation results are filtered before ranking. A large required context, local-only privacy mode, a restrictive team model profile, or a custom catalog with few eligible records can leave one fitting candidate. This is different from having only one model installed in the catalogue.

First confirm the dashboard's catalogue count. Then reduce selected context with ignores or a repo map, review the goal and privacy mode, and check team provider or model allowlists. TCalc keeps the three tiers distinct when enough eligible candidates exist; it does not fill them from raw catalog order.