SaveMyToken logoSaveMyToken.
← All agent setup guides

CONFIGURATION, EXPLAINED

DeepSeek Harness (DSH) Config: Models & API Setup

Read DSH's real YAML provider patches, reasoning and output limits, third-party models, compaction, permissions and MCP. Select a setting to see its explanation.

Official sources reviewed 2026-10-08One config · select a setting to read its explanation
$DSH_HOME/profiles/web/cordis.patch.yml

One continuous config. Click a line for its explanation. Commented lines show optional settings, alternatives or separate setup; the copy button includes active settings only.

YAML CONFIGSections are marked inside the codeSELECTED SETTINGOnly what you click is explained here
# ── Official connection ──

Official connection

Target the installed plugin entry

llm-deepseek.id

Identifies the Cordis entry this patch changes.

In the main config$DSH_HOME/profiles/web/cordis.patch.yml
In this example
"llm-deepseek" is the example value; it is not a universal recommendation.
If you leave it unset
Omission leaves this choice to the installed version, provider and higher-priority configuration.
When to change it
Keep llm-deepseek for the shipped official API-key route.
What changes / what to watch
This adapter serves deepseek-official. A config override replaces the entry's entire config; preserve your existing fields when merging.
Check that it worked
Reload the intended file or start a fresh session. Inspect the active model, tools or setting, then check one small task before relying on the change.
Official reference ↗

Copy keeps the parent structure. Merge it into the file shown above.

config:
retryPolicy:
# ── Connection alternatives & separate-file setup ──
# $DSH_HOME/profiles/web/cordis.patch.yml
# config:
# providers:
# example:
# retryPolicy:
# models:
# Agent preset → compaction-basic → config
# Active composition → permission-presets → config
# presets:
# workspace-write:
# $DSH_HOME/profiles/web/cordis.patch.yml
# - insert:
# config:
Official connection · llm-deepseek.id

Find an explained key & its source

SETTINGS AND OFFICIAL SOURCES

Explained settings index

This index covers the settings explained in this handbook. Follow the official sources for the complete schema, additional plugins and platform-specific options. The index is not a file to paste, and not every key is available in every client or scope.

39 of 39 documented entries · showing 30

Setup, troubleshooting & official sources

Where settings take effect

DeepSeek Harness (dsh), official source revision 5badb15009ae. The standard web profile uses $DSH_HOME/profiles/web/cordis.patch.yml (DSH_HOME normally ~/.dsh). Plugin configs and Agent preset internals have distinct owners; inner fragments are marked explicitly.

  1. Start the intended profile and use Settings → Models for the official DeepSeek API-key route or an included provider. Select the model in the picker; an existing session can retain its recorded model.
  2. For the web profile, edit its cordis.patch.yml. A config override replaces an entire entry config, so preserve all existing provider and plugin fields when merging examples.
  3. Agent preset settings such as compaction live inside that preset's plugin composition. Use its editor to find the owning plugin; do not paste those inner fragments at the profile root.
  4. Credentials are separate from the visible patch. Use the supported settings/sign-in flow; never publish .credentials.yaml or real token values.

OFFICIAL AND THIRD-PARTY ACCESS

Choose how the agent connects.

Use one model-provider route per session. MCP connects tools and data; it does not replace model authentication.

Official DeepSeek API key

llm-deepseek entry, serving deepseek-official over Messages.

Authentication
DEEPSEEK_API_KEY credential reference.
Verify
Choose a served model and inspect the selected provider.
Open annotated setup →

Included providers & custom gateways

llm-pi-ai providers map.

Authentication
apiKeyEnv or the installed provider's supported sign-in mechanism.
Verify
Protocol, catalog and exact model capabilities must match.
Open annotated setup →

MCP tools

A separate MCP client plugin.

Authentication
The server's documented credentials or sign-in.
Verify
Inspect plugin startup and discovered tools.
Open annotated setup →

AFTER YOU EDIT

Check the effective settings.

  1. Check the installed revision and plugin IDs before applying a patch.
  2. Validate YAML and inspect plugin-load errors; unknown fields can reject configuration.
  3. Keep other providers when editing the llm-pi-ai config and confirm the session's selected route.
  4. Check compaction and permission changes inside the intended Agent preset.
  5. Documentation review and syntax checks do not constitute a live gateway or billing test.

Documentation-based examples. No live model calls or measured cost savings are claimed.

COMMON QUESTIONS

A few useful distinctions.

Is DSH configured with settings.json?

The provider examples here are Cordis YAML patches. Credentials, per-session model choice and Agent preset plugin configs are separate state; a generic settings.json would not represent those layers.

Is DSH's pi-ai adapter the same config as Pi?

No. They can share adapter technology while exposing different schemas. DSH uses providers under a plugin config, baseURL, apiKeyEnv and reasoningEfforts; Pi's models.json uses its own fields.

Official sources

Checked 2026-10-08. Follow the documentation for your installed version and selected model.

Back to the DSH profile →