Skip to main content
DeepSeek’s coding agent (dsh) runs named profiles, such as tui, web, and headless, under $DSH_HOME, which defaults to ~/.dsh. Restart dsh after changing a profile. Generally available OpenAI Chat Completions Nexus Auto

Quick start

Install and sign in

You need Node.js 22 or later, git, and bash. On Windows, run the installer from Git Bash. PowerShell breaks the script’s line endings.
Sign in with your browser, or paste a Fireworks API key (fw_...).Already set up? Skip to step 2.

Connect DeepSeek Harness

Restart and pick a model

Restart dsh. It starts on auto and goes straight to Fireworks, with no DeepSeek key prompt. To change the default, run nexus deepseek --model glm-latest.
nexus deepseek status shows the provider, where the key comes from, and the configured model.

Use Nexus Auto

Nexus Auto (auto) is supported on the Chat Completions API.
  • Anthropic and OpenAI model turns: save a key with nexus auto --anthropic-api-key or --openai-api-key (each prompts for the key), then run nexus deepseek again. Nexus CLI adds the saved key to the fireworks provider headers. Or connect a Provider Key, which needs nothing saved locally.
  • Environment keys: Nexus CLI never sends ANTHROPIC_API_KEY or OPENAI_API_KEY from your environment.
  • Manual setup: send x-anthropic-api-key and x-openai-api-key headers yourself. See Manual setup (advanced).

MCP and tools

Nexus CLI doesn’t touch MCP. Set up servers in dsh as usual. Nexus CLI does not add web search to DeepSeek Harness. See Web Search.

Microsoft Foundry

Nexus CLI doesn’t connect DeepSeek Harness to Microsoft Foundry. For other options, see Nexus for Microsoft Foundry.

Troubleshooting

See Nexus Auto for issues that affect every harness. Upgrading from an earlier version? See Upgrading from earlier versions.

Manual setup (advanced)

Create the profile folder once, then add a patch to it. Repeat for each profile you use. On dsh 0.2 and later, you can put the same patch in ~/.dsh/cordis.patch.yml instead to cover every profile.
~/.dsh/profiles/tui/cordis.patch.yml
To use Nexus Auto with Anthropic or OpenAI model turns, add headers to the provider, such as x-anthropic-api-key: sk-ant-..., and use auto as the model. The harness setup generates the full patch. See what changes without the Nexus CLI.

What the Nexus CLI writes

Nexus CLI writes the fireworks provider and default model to three layers, so every dsh version picks them up:
  • ~/.dsh/settings.yaml
  • ~/.dsh/cordis.patch.yml, the home-level patch that dsh 0.2 and later apply to every profile, including new ones
  • Each existing profile’s cordis.patch.yml, which dsh 0.1.7 and later read
Your key goes to ~/.dsh/.credentials.yaml as FIREWORKS_API_KEY.
~/.dsh
settings.yaml
cordis.patch.yml
.credentials.yaml
profiles/<profile>
cordis.patch.yml
~/.dsh/settings.yaml
~/.dsh/.credentials.yaml
The patch files carry the same provider and model as llm-pi-ai and agent-default-model entries. The x-anthropic-api-key and x-openai-api-key headers appear only for keys you saved with nexus auto. Nexus CLI also adds its own attribution headers.Every file is saved with mode 0600. off restores each one byte-for-byte from the snapshot under ~/.nexus/deepseek/, and deletes the ones Nexus CLI created. Use --config-path for a settings.yaml stored elsewhere. Nexus CLI then keeps the credentials file and patches in that folder.