webdsh

webdsh DeepSeek Harness in a browser tab — the real agent, real Node, no server to run.

DeepSeek Harness (dsh) is an agent harness where everything is a plugin. dsh web runs a Node host and serves a browser client to it. webdsh is that, as static files — the host runs inside the page, and the agent's commands run in WebContainers: Node itself, in the tab. ⚡ Nothing to run. No server, no install, no local Node — the harness boots in the page. 🌍 The container is online too. The page's CORS policy is preloaded into every Node process it starts, so fetch inside the container retries a refused host through the proxy on its own — http://example.com answers there now, and it did not before. 🖥️ Real Node, real Python. npm install and pip install both work, and the terminal and the agent share one container. 💾 Or a whole PC. Settings → Machine swaps the container for v86 and offers 128 machines — the whole of v86's catalog, from a 512-byte bootsector game to Windows 2000, 127 of them booting with nothing to set up — emulated x86, on its own screen, with the tool set that machine actually has. 🧭 Or a browser. The third machine is real tabs of the real web, and the assistant drives them three ways: the page structure (a labelled tree with a handle on everything c

Nothing here is a fork of dsh. The agent loop, tool registry, model adapters and the entire web client come from npm at install time; the only modification is a cordis.patch.yml layer — the mechanism dsh documents for exactly this.

What this repository adds is the platform underneath: a synchronous POSIX filesystem mirrored to IndexedDB (src/vfs), node:* implemented over it (src/node), the runtimes a session can run on — WebContainers and an emulated x86 PC (src/runtime), and a browser built out of sandboxed frame