DeepSeek Harness (developer preview) is a local Agent runtime. See deepseek.com/harness and deepseek-ai/deepseek-harness. Teams usually start the Web UI with npx @deepseek-ai/dsh web at http://127.0.0.1:3080. Remote access should prefer an SSH local forward into loopback—do not bare-expose a writable Agent port. Sessions are traceable (Trajectory: resume, fork, search, replay), which is not the same as turnkey multi-user SaaS. Use Youdao lookup or text translate to understand English docs/errors; install the client from /en/download/. Solo doc/error flow: Harness docs + Youdao.
Small teams rarely fail on “can we run npx?” They fail on who owns which host, how remotes reach the UI, how sessions are handed off, and how keys/workspaces stay unshared by accident. Deploy, remote, share, Youdao, stop—below.
127.0.0.1. Understand English wording → Youdao. Install the translate client → download page. Clearing Youdao cache is not a Harness deploy step.
Team Web deploy: make local work before “sharing”
Public quick start: install Node, then npx @deepseek-ai/dsh web. A desktop launch often opens a browser at 127.0.0.1:3080. From source, clone, follow the README build, then use the repo’s dsh web entry—trust the revision you checked out. Preview builds change plugins and APIs; teams should pin versions (npm package or git commit) and document one reproducible command set so everyone does not land on a different preview.
Working directory matters: where you start often becomes the default workspace root. Keep a demo repo separate from sensitive trees; do not mount a home directory full of secrets into a writable Agent. Tighten model keys and credential file permissions per your host policy—Youdao helps you read English warnings; it does not store API keys for you.
Public pages stress “everything is a plugin”: models, tools, skills, sessions, sandbox, storage, scheduling, UI. Mode names (Standard / Code / Minimal / Creator, or whatever your page shows) follow live docs. Agree on a default mode and allowed tool surface; fewer surprises than each person improvising Creator experiments.
Remote teammates: SSH forward, not a public :3080
The official README notes a local launch opens the browser; an SSH launch usually only prints the host-side URL because the SSH client or editor owns the forwarded address. Use --no-open when you want the server without opening a browser (confirm flags with current CLI help). Loopback-only listening is a local control surface, not “anyone on the LAN may click.”
Practical remote pattern: start dsh web on the server (often with --no-open), open a local port forward from the laptop, then browse the laptop’s 127.0.0.1:3080 (or the local port you chose). Tunnel up but connection refused usually means nothing listens on the far side—check the remote listener before blaming Youdao or a browser extension.
Binding the Web UI to all interfaces, or publishing 3080 to the internet, hands a file-and-shell Agent control plane to anyone who can reach the port. Community discussion already covers missing dedicated login and loopback-sharing risks on multi-user hosts. Default to a tight exposure surface in preview. If you need HTTPS or an authenticating reverse proxy, read current Web/security docs and let infra review—this article will not ship a “one-click public open” recipe.
What “share” means: traceable sessions ≠ one writable multiplayer instance
Public messaging records what the model sees in an append-only session log. Trajectory views inspect by source and support resume, fork, search, and replay. That helps teams: review a bad tool call, fork a trail for a coworker, instead of describing “the Agent randomly edited files.”
“Share” is often misread as one forever-on Harness that the whole group logs into. Preview reality is closer to one writable instance per person or task host, reproduced with the same pinned version and config. Hand off session records, config snippets, and repo commits—not a credentials-laden $DSH_HOME dump on a shared drive. Concurrent writers on one session root invite single-writer pain—if ops docs mention isolating session roots, follow them.
The plugin ecosystem allows third-party UI extras (read-only snapshots, local export “share” flows). Those are not a first-class “team workspace” product on the marketing homepage. Before install, verify publisher, version, and profile; keep the main UI on loopback and confirm whether the share surface is read-only. Official diagnosis still prefers full session-log export; a human-readable summary is not a lossless forensic pack.
Terminology collaboration: shared glossary + Youdao lookup
Teams fight less over UI than over inconsistent glosses: “会话” vs Session, each person renaming plugin / Trajectory / sandbox / profile. Keep an internal glossary: English tokens stay fixed, Chinese glosses may localize, package names and CLI flags never rewrite. Short UI labels → Youdao lookup/selection; whole README or security sections → text translate for gist, then copy commands from English.
On-call stacks: Youdao for gist only (deps, port, permissions, network); search Issues in English. If paths become Chinese or full-width punctuation appears, trust the terminal. Mojibake → garbled-text article. Solo doc flow is not repeated here—see Harness docs + Youdao. Boundaries: translate vs dictionary.
Onboarding checklist: “Node matches the current README” and “Youdao installed; can translate one English sentence.” Wrong platform or bad updates → download page / update-failure posts—do not reinstall Node as a charm.
Install Youdao from the download page only
Platform packages and notes follow /en/download/. After install, translate one short English line, then return to Harness materials or SSH errors. Do not treat the Harness repo, an npx line, or a “Harness APK” as a Youdao installer.
When to stop
Local dsh web works and docs make sense, but remotes fail: check tunnel and remote listener—do not reinstall Youdao. Sessions replay but coworkers cannot reproduce: align pinned package/commit and cwd; do not share credential directories. npx fails: README / Discussions, Node, network. Preview menus or flags renamed: trust the CLI/docs you have open; stale screenshots are hints only.