Delorun and stock DeepSeek HarnessCopy Anchor Link

English | 中文

SummaryCopy Anchor Link

This page helps you decide whether Delorun suits you, and what changes if you come from stock DeepSeek Harness. You need nothing first. Stock DeepSeek Harness (DSH) is the harness as its own maintainers release it (stock DSH).

Delorun is a community fork of DSH. It runs DSH's own code, keeps DSH plugins and chats working, and installs and works like stock DSH: on your computer, with no account, and one command that opens the studio. On top of that it adds its own studio look, updates that show what they would change and can go back, protections around the commands the model runs, and remote access from your phone over your own tailnet. You can switch back to stock behaviour for each addition that changes what the model sees. This page lists what stays the same, every difference you notice, and what Delorun does not include. The roadmap says what is planned.

ContentsCopy Anchor Link

• Why Delorun exists
• What stays the same
• What is different
• Defaults that differ
• What Delorun removes
• What Delorun does not include
• Moving between DSH and Delorun
• Roadmap and vision
• For the technically curious

Why Delorun existsCopy Anchor Link

DSH is an excellent harness, and its maintainers do not accept outside contributions. Delorun is where the community can change any part of it: the studio, the harness, its plugins and its defaults. Its aim is that anyone using it can have many capable agents working with them, on their own work and their own machines, under their control.

Delorun holds itself to these rules:

• Stock first. A fresh install follows the stock DSH workflow. Delorun sends nothing about you. Its default network requests are a check of the public release log at each start and a daily check for a newer release, which Settings, General, Updates turns off (What you trust when you use Delorun).
• Yours to change. Configuration, plugins, presets, skills, themes and the studio are yours, and no hidden layer overrides them.
• Updates never take your work away. Before an update you see what it would change, your profile is saved first, and one command goes back (Updates).
• Delorun cannot get in on its own. Your studio runs on your computer, and every new device needs your approval at that computer (Reach the studio from your phone).
• Honest claims. A protection is called enforced only where a test proves it, and this guide states what Delorun does not include.

What stays the sameCopy Anchor Link

• The harness. Delorun runs DSH's own code at a named DSH release; delorun --version prints both versions.
• Compatibility. Plugins, presets, skills, profiles and chats work as in DSH. Before a change is accepted, DSH's own recorded scenarios are replayed with every Delorun change that the model can see switched off, and they must give the same results.
• Modes. DSH's four agent presets, Standard, PTC, Minimal and Creator, are offered in every new chat, and Standard is the default.
• Model providers. The providers DSH supports, set up the same way.
• The licence. MIT.

What is differentCopy Anchor Link

Edge cases

• If you run on Windows, then commands can read Delorun's home, its secrets and its token, though they cannot write there — treat the model's commands as able to read them (What Delorun protects).
• If you run on Linux without bubblewrap on a desktop, then Delorun refuses to run sandboxed commands at all — install bubblewrap.
• If you chose Ask less (like DeepSeek Harness) in setup, then the full-access, instruction-file, MCP server and scheduled-task consents are off, and the network setting is not available — run delorun setup prompts to choose Ask me first again.
• If you want the stock look, then choose Stock in Settings, General, Look — Delorun look in the same place switches back.

Defaults that differCopy Anchor Link

The parity checklist lists each changed default with its evidence:

• Delorun's studio additions are on; the stock look is one switch away in Settings, General, Look.
• A new workspace starts on Workspace Write whatever the deployment default is, and with Ask me first full access needs your consent once per workspace.
• DeepSeek's session-log upload is off until you turn it on.
• web_fetch refuses loopback, link-local and private-network addresses.
• Commands the model runs cannot write to or read Delorun's home, or reach its control socket, where your system enforces it.
• With Ask me first, the instruction-file, MCP server and scheduled-task consents apply. Setup's Ask less (like DeepSeek Harness) answer turns them and the full-access refusal off (Ask less (like DeepSeek Harness)).
• The default workspace is Delorun/default-workspace in your Documents folder, or in your home folder when your system names no Documents folder.

Other differences exist in the code but are off in the profile delorun runs, so DSH's behaviour stands for each. The parity checklist names them.

What Delorun removesCopy Anchor Link

• DeepSeek's account and Platform integration: no Platform sign-in, Usage or Top-up page. Delorun works with any model provider DSH supports, DeepSeek's API with your own key included.

What Delorun does not includeCopy Anchor Link

Delorun does not include these, and this guide describes each only where it affects a choice:

• a Delorun desktop app, and macOS and native Windows releases;
• Docker workspaces, where a workspace's commands run in a container;
• reach through Tailscale Funnel or your own relay on your own domain, and sign-in with a passkey or your own sign-in provider;
• delorun verify checks of isolation, exposure, sign-in, plugins and data sharing, which the report lists as not run;
• a community plugin catalogue with "tested with Delorun X" badges, and a revocation list for known-bad plugin versions;
• ejecting a plugin while keeping its settings in your profile;
• the main chat, importing a workspace with git clone and editing its AGENTS.md from the studio, which exist as plugins that no profile loads;
• PTC as the default mode in the first-run guide.

The roadmap says which of these are planned.

Moving between DSH and DelorunCopy Anchor Link

• From DSH: setup offers to copy your chats and workspaces from ~/.dsh, and delorun import-home does it any time and asks about your profiles, settings, instructions, skills and key one by one. ~/.dsh is never changed (Switching from DeepSeek Harness).
• Back to DSH: your DSH home stays untouched, so stock DSH keeps working beside Delorun. delorun export writes chats and workspaces as files that another home imports.
• Stock behaviour inside Delorun: turn off Delorun's studio additions for the stock look, and answer Ask less (like DeepSeek Harness) in delorun setup prompts for DSH's prompts.

Edge cases

• If ~/.dsh is a link and not a folder, or your Delorun home already has chats, then setup does not offer the copy — run delorun import-home yourself.
• If you use both after importing, then chats you start in Delorun stay in your Delorun home — use delorun export to take them elsewhere.

Go further

• delorun import-home --dry-run shows what would be copied and writes nothing.
• delorun export and delorun import move chats and workspaces between Delorun homes.

Roadmap and visionCopy Anchor Link

What Delorun is for, what is planned and in what order, and what is not planned are on Roadmap and vision.

Next. To install Delorun, read Install and first run. To keep your DeepSeek Harness work, read Switching from DeepSeek Harness. If something went wrong, find its message in Troubleshooting.

For the technically curiousCopy Anchor Link

The parity checklist lists every difference from stock with its evidence, including switches such as preset_inspect, profile-history actions for the model and the container denial marker that are off in the profile delorun runs. The delorun/docs/contracts/c16-parity-composition.md defines how Delorun proves it still behaves like stock with its changes switched off. Plugins, presets, skills, profiles, bundles, client slots and chats keep DSH's ids and wire formats, which that contract checks.