Back to SinWeave
NEW · OPEN SOURCE deepseek harness — the runtime, not the model

The open agent runtime, running inside your editor.

In August 2026 DeepSeek open-sourced Harness — the agent runtime their own models were built to run in. Not a model, not an API: the loop that reads your files, calls tools, runs commands, and keeps going. It is MIT-licensed, and it is coming to SinWeave.

Fig. 07 harness · agent run · 14 steps
you the checkout tests are flaky. find out why and fix it.
harness Running vitest checkout ten times to reproduce. 3 of 10 failed on cart.total — a shared fixture is mutated between cases. Patching the fixture, then re-running.
  18- const cart = baseCart
  18+ const cart = structuredClone(baseCart)
  31  expect(cart.total).toBe(4200)
14 steps · 2 files · 10/10 green · sandbox: workspace-write
§ 01

everything is a plugin

Most agent tools hard-wire the loop and let you swap the model. Harness inverts that: every layer is a plugin, including the loop itself. That is the whole reason it is worth adopting rather than reinventing.

The model layer

DeepSeek V3.1 is the default, but inference is a plugin like everything else. Point it at Anthropic, OpenAI, Gemini, OpenRouter, or the Ollama instance already running on your laptop.

A real sandbox

Commands run under an enforced file policy — read-only, workspace-write, or full access if you insist. Landlock and bubblewrap on Linux, Seatbelt on macOS, restricted tokens on Windows.

Long runs that survive

Context compaction, spill-to-disk, session storage, and checkpoints are first-class packages. A run that takes forty minutes and two hundred tool calls does not fall over halfway.

Subagents and workflows

Fan work out to child agents, each with its own budget and toolset. Plans, goals, and todo state are tracked by the runtime rather than improvised inside a prompt.

MCP, LSP, hooks, skills

Model Context Protocol servers attach directly. Language-server diagnostics feed the agent real type errors. Hooks let you intercept any tool call before it runs.

An auditable trail

Every step is recorded: which plugin fired, which tool it called, what came back. When an agent does something surprising you can read exactly why instead of guessing.

Upstream deepseek-ai/deepseek-harness — the reference implementation we build on
Licence MIT — permissive, forkable, no strings on what we ship
Released August 2026 — crossed 200,000 GitHub stars inside its first month
Written in TypeScript, on the Cordis plugin framework — the same language SinWeave is
Status Developer preview upstream. Breaking changes expected, which is why we are taking our time
§ 02

what changes for you

SinWeave already does chat, inline edits, and multi-file diffs well. Harness is about the jobs that are too long or too branching for a chat window.

With Harness SinWeave today
Task length Hundreds of steps, compacted and checkpointed as it goes Great for a file or a feature, strained by an afternoon of work
Running commands Tests, builds, and scripts under an enforced write policy You run them, then paste the output back
Parallel work Subagents with their own budgets and tools One conversation at a time
Tool ecosystem MCP servers, LSP diagnostics, hooks, community plugins The built-in toolset
Your keys Unchanged — straight from your machine to your provider Unchanged — straight from your machine to your provider
Price Free — you pay the model provider, or nothing if local Free — you pay the model provider, or nothing if local
§ 03

how it will run

The plan is deliberately boring: the runtime sits beside the editor, speaks a documented protocol, and never becomes something you cannot turn off.

  1. 01

    The runtime ships inside SinWeave.

    No separate install, no daemon to babysit, no account. It starts with the editor and stops with it, and you can disable it entirely in Settings.

  2. 02

    Your existing keys carry over.

    Whatever you have already configured becomes the harness's model layer. Nothing new to paste, and no provider you did not choose yourself.

  3. 03

    You watch, and you keep the veto.

    Every step appears as it happens and every write still lands as a reviewable diff. The sandbox policy is yours to set — read-only, workspace-only, or open.

Adopting Harness does not change the deal. The runtime executes on your machine against your files. Prompts and code go to the provider you picked and nowhere else. We do not proxy it, we do not log it, and there is still no SinWeave account.

Early access

be there for the first build

We will send one email when the Harness build is ready to try, and a second if we need testers before that. No newsletter, no drip sequence, no sharing your address with anyone.

One email, then silence until it ships. Unsubscribe is a reply. Harness itself is open source — you can read every line at deepseek-ai/deepseek-harness.

§ 04

questions

Does this mean SinWeave is becoming a DeepSeek product?

No. Harness is MIT-licensed software that happens to have been written by DeepSeek, in the same way SinWeave is a fork of software written by Microsoft. The model layer is a plugin — DeepSeek V3.1 is the default because that is what upstream ships, and you can replace it in one setting.

Will my code be sent to DeepSeek?

Only if you choose a DeepSeek model, and then it goes directly from your machine to their API with your own key. Pick Anthropic, OpenAI, or a local Ollama model and DeepSeek never sees anything. The runtime itself is code running on your laptop, not a service.

Why adopt someone else's runtime instead of building our own?

Because the hard parts — sandboxing across three operating systems, context compaction, session recovery, subagent budgets — are solved there and battle-tested by a very large number of users. Writing a worse version of that ourselves would cost months and buy nothing.

When does it ship?

No date yet. Harness is still a developer preview and its own authors warn about breaking changes, so we are tracking it rather than racing it. The waitlist is the honest answer: you will hear the day there is a build worth using.

Will it cost anything?

No. SinWeave stays free and Harness is MIT-licensed. You pay your model provider directly, or nothing at all if you run local models. Long agentic runs do burn more tokens than a chat message, so keep an eye on your provider dashboard.

Can I try Harness right now, outside SinWeave?

Yes — it is open source and runs standalone today. That is a separate thing from the SinWeave integration, which is what this page and the waitlist are about.