Configure DeepSeek Harness Models and Providers
Open Settings → Models in the local DeepSeek Harness Web UI. Save a DeepSeek key, add a catalog-backed third-party provider, or create a custom provider with its exact protocol and model IDs. Then select a model for a new session. Saving a card and obtaining a successful model response are separate checks.
Sharing includes the public link only, without local progress or private configuration.
Configure the DeepSeek model card
Enter the DeepSeek API key in the local Models card and save. The reviewed page stores the key in $DSH_HOME/.credentials.yaml and retains a reference in settings. The browser receives a redacted descriptor after saving, rather than the secret. This field guide does not receive or validate your key.
Choose a third-party or custom model provider
For a provider in the shipped catalog, choose Third-party model provider and use its provider ID and key. The catalog supplies the endpoint, protocol and model list. For a gateway absent from the catalog, choose Custom model API and provide a permanent lowercase ID, base URL, protocol, credential and at least one model.
- The reviewed Models page does not support OAuth sign-in for third-party providers such as Codex.
- A custom provider uses one protocol; create separate providers when the gateway exposes two protocols.
- Check the installed package version before relying on a newer GitHub UI option.
Select a model in a fresh session
Selecting a model also sets the default for new sessions. A session that already sent a request retains its recorded model. If a deleted provider leaves the default invalid, select an available model before entering a task. Confirm both the provider and model ID in the new session.
Diagnose the first request
Start with a small repository question you can inspect. MISSING_CREDENTIAL means the selected route cannot resolve its key reference; UNKNOWN_MODEL in the pi-ai adapter means the model is not configured. A 401 from discovery points to authentication. A request-format rejection points to the protocol or compatibility fields.
- Fix one layer, save it, then repeat the same request.
- Keep keys out of screenshots and sanitized issue logs.
First-party sources
Open the pinned or retrieved source before acting on a changed release candidate.