m11s/deepseek-harness repository overview

⁠m11s/deepseek-harness

DeepSeek Harness (DSH) web runtime, with an optional browser provider attached to a separate Chromium CDP container. The DSH image does not install Chromium.

⁠Run

Set a DeepSeek API key, then start the deployment:

export DEEPSEEK_API_KEY=...
docker compose up

Open http://localhost:3080⁠. The dsh-home named volume persists DSH state at /home/dsh/.dsh; ./workspace is mounted at /workspace for project files. Local Compose pulls the published m11s/deepseek-harness:0.1.6-alpha.1 image; it never builds the DSH source image locally. The companion Chromium image may still be built locally.

The Compose example starts Chromium privately for browser features. It does not publish CDP port 9222; DSH connects over the Compose network at http://chromium:9222. Chromium's own sandbox is retained. Its Compose service uses seccomp=unconfined so Docker Desktop permits Chromium's sandbox namespace setup.

⁠Separate Chromium deployments

When Chromium runs outside this Compose project, set DSH_BROWSER_CDP_ENDPOINT to its reachable CDP endpoint. For example:

DSH_BROWSER_CDP_ENDPOINT=http://browser.internal:9222 docker compose up

The browser provider is optional; DSH can be used without browser automation.