DeepSeek Harness Config Files: Profiles and Override Order
When an edit appears to have no effect, first check which profile you launched and whether a later configuration layer replaces it. In the reviewed CLI, overrides replace the targeted row’s complete config value; they are not a recursive merge of individual keys.
Sharing includes the public link only, without local progress or private configuration.
Locate the active profile
The standard web launch uses the web profile under $DSH_HOME/profiles/web. A named custom profile has its own directory. Read the launch command before choosing a file.
- Back up the file you intend to edit.
- Keep credentials as references rather than inline secret values.
Follow the precedence order
The CLI composes bundle patches, the profile patch, the home-level patch and then command-line --patch overlays. A later row can replace an earlier row’s complete config. Preserve other provider entries when editing an existing row.
Inspect before starting work
Run dsh --profile web --dump-config to inspect the composed tree for web. It can initialize missing profile files, so use the profile you intended. The dump is configuration evidence, not a successful provider request.
- Compare the effective provider configuration with your intended edit.
- Remove credentials and private addresses before sharing output.
- After inspection, validate with a fresh session and a small task.
First-party sources
Open the pinned or retrieved source before acting on a changed release candidate.
- Official docs/user/guide/providers.mdOfficial documentation · retrieved 2026-10-04↗
- Official apps/cli/reference/README.mdOfficial documentation · retrieved 2026-10-04↗
- Official packages/llm/llm-deepseek/README.mdOfficial documentation · retrieved 2026-10-04↗
- Official packages/llm/llm-pi-ai/README.mdOfficial documentation · retrieved 2026-10-04↗