togetherlink
Alpha integration · developer preview · 7 min

Try DeepSeek Harness with Together AI Models

Open DeepSeek Harness's browser UI with a temporary Together provider and model selection. DSH remains the agent interface; Together serves the model.

By TogetherLink

TLtogetherlinkALPHA PROVIDER PATCHTry DeepSeek Harnesswith Together AI models$tdeepseek4 open models · Chat CompletionsDeepSeek HarnessPOWERED BY

The short answer

TogetherLink launches dsh web with a credential-free Cordis patch that adds Together's curated catalog. The key is supplied only to the DSH process, and the normal DSH configuration is not rewritten.

Install and launch

Start a first Together-backed session

1

Install DeepSeek Harness

Use the upstream project's supported installer. See the DeepSeek Harness repository for platform-specific options.

$npm install -g @deepseek-ai/dsh
2

Install and configure TogetherLink

Save a Together API key once. The selected model is billed by Together AI, not by the harness vendor.

Install TogetherLink
$curl -fsSL https://togetherlink.vercel.app/install.sh | bash
Save the API key
$togetherlink configure
3

Launch DeepSeek Harness

Install if needed, then open on Kimi K3
$tdeepseek
Use DeepSeek V4 Flash on another port
$togetherlink --model deepseek-ai/DeepSeek-V4-Flash-0731 deepseek --port 4080

What TogetherLink changes—and what it leaves alone

AreaBehavior
Model requestsThe harness calls Together AI directly through its OpenAI-compatible API.
Together keyProvided only to the launched process; it is not written into the generated provider metadata.
Harness stateTogetherLink does not rewrite DSH's normal user configuration. Native DeepSeek models remain available only when DEEPSEEK_API_KEY is already set.
Provider setupA credential-free, content-addressed Cordis patch is stored under ~/.togetherlink/deepseek-harness and passed with --patch for this launch.
Usage reportingTogetherLink records launch lifecycle only. Token and cost totals are not available locally for this direct harness.

This is an alpha adapter for a developer-preview harness

DeepSeek explicitly warns that DSH is iterating rapidly and may make compatibility-breaking changes. Keep TogetherLink current, and treat the generated web workflow as experimental.

Keep the harness

Together changes the model, not the workflow

Browser UI

DSH serves its web interface on 127.0.0.1:3080 by default; port flags pass through normally.

Plugin architecture

The Together provider is added as a Cordis patch without replacing the harness or its plugin system.

Demand install

TogetherLink installs DSH only after you explicitly invoke or select it, never during configure or startup.

Native provider boundary

Without DEEPSEEK_API_KEY, native DeepSeek models are hidden so the active provider choice is unambiguous.

Curated model catalog

5 curated models, with Kimi K3 as the default

To override the model, put --model before the harness name. Arguments after the harness name belong to the underlying tool.

Kimi K3
moonshotai/Kimi-K3

Default · vision · reasoning · 1M context

GLM 5.2
zai-org/GLM-5.2

text · reasoning · 512K context

DeepSeek V4 Pro 0813
deepseek-ai/DeepSeek-V4-Pro-0813

text · reasoning · 1M context

Qwen 3.7 Max
Qwen/Qwen3.7-Max

vision · reasoning · 1M context

DeepSeek V4 Flash 0731
deepseek-ai/DeepSeek-V4-Flash-0731

text · reasoning · 1M context

Verify the launch before starting work

TogetherLink prints a launch line before the harness opens. For the default command, look for:

togetherlink ▸ Launching DeepSeek Harness web UI with Together AI (alpha).

Launching the upstream binary directly skips TogetherLink and uses that tool's normal provider configuration.

Common questions

FAQ

Can DeepSeek Harness use Together AI models?+

Yes. TogetherLink starts DSH's web UI with a generated Cordis patch that adds the curated Together provider and selects the requested model.

Do I need to install DSH first?+

Not necessarily. If dsh is missing when you explicitly run tdeepseek or select DeepSeek Harness, TogetherLink installs @deepseek-ai/dsh globally with npm and then launches it. No other harness is auto-installed.

Why is this integration labeled alpha?+

DeepSeek calls DSH a developer preview and warns that compatibility-breaking changes are expected. TogetherLink labels the adapter alpha for the same reason.

Where does the web UI open?+

DSH serves its web UI at http://127.0.0.1:3080 by default. Pass DSH options after the harness name, such as: togetherlink deepseek --port 4080.

Does TogetherLink report DSH token cost?+

No. DSH calls Together directly, so TogetherLink records session lifecycle but does not see the inference stream or produce local token and cost totals.

Related guides