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 with manual setup

Quick start

Install and sign in

Requires Node.js 18 or later, git, and bash. On Windows, run it from Git Bash; PowerShell breaks the script’s line endings.
Sign in with your browser, or paste a Fireworks key.Already set up? Skip to step 2.

Connect DeepSeek Harness

Restart dsh

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

Use Nexus Auto

Nexus CLI can add auto, but it does not send provider keys from dsh. For turns on Anthropic or OpenAI models, connect a Provider Key or use manual setup to send x-anthropic-api-key and x-openai-api-key headers.

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.

Troubleshooting

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.
~/.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 adds a fireworks provider to ~/.dsh/settings.yaml and to each existing profile’s cordis.patch.yml, which dsh 0.1.7 and later read. off restores both from the snapshot under ~/.nexus/deepseek/.
~/.dsh
settings.yaml
.credentials.yaml
profiles/<profile>
cordis.patch.yml