Surfaces: Web, headless, SDK

Goal

Pick the right entrypoint for DeepSeek Harness: interactive Web UI versus automation-oriented surfaces.

Web UI (most beginners)

Started via npx @deepseek-ai/dsh web. Best for exploring settings, watching tool calls, and teaching teammates. Local URL is typically http://127.0.0.1:3080/.

Headless / CLI-oriented flows

Public docs describe headless and CLI usage for scripts and servers without a browser. Prefer these when you already know the workspace and want repeatable jobs.

TypeScript / Python SDK paths

SDKs help embed harness behavior into your own apps or research harnesses. Confirm package names and versions in the official repository — previews move quickly.

Choosing for CI

• Interactive debugging → Web UI on a secure machine.
• CI agents → headless/CLI with pinned versions and least-privilege credentials.
• Product integration → SDK with explicit allowlists for tools and paths.

Security note

Any surface that can run shell or edit files needs a scoped workspace and reviewed plugins. Trajectory logs (next chapters) help you audit what happened.

Next

Learn how the plugin ecosystem and dsh-plugin discovery work.