Evidence record / deepseek-harness

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-deepseek-harness-rc-3-discovers-official-api-key-models-dynamically-instead-of-relying-only-on-the-bundled

Rc.3 discovers official API-key models dynamically instead of relying only on the bundled catalog. The API-key route can follow the official /models listing, as the account route already does. It applies only to the official origin with the unmodified built-in catalog, refreshes in the background, and retains a last usable or built-in fallback. A listed model marked unsupported by this client is refused before inference I/O; an unlisted custom ID is not automatically forbidden. Custom endpoints or explicit catalogs keep their own policy. Rc.2 separately introduced support for DeepSeek-V4.1-Flash-1017.

Channel: preview-or-beta. Half: capability. Date: 2026-10-23.

Operator consequence: Choose rc.3 explicitly if reducing manual catalog updates matters; staying on npm latest does not obtain this change. Keep explicit model and endpoint choices for reproducible trials. A newly visible model is an availability signal, not evidence of better coding performance or a silent model migration. Catalog maintenance becomes cheaper while task-level model evaluation remains necessary.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-deepseek-harness-rc-3-discovers-official-api-key-models-dynamically-instead-of-relying-only-on-the-bundled

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact