Daily use
English
Summary
This page shows the commands you use every day and the choices you make about what the model may change. It assumes Delorun is installed and set up (Install and first run). Delorun runs as one background program per profile, the home process, which serves the studio in your browser. A few commands start, open, stop and check it. Each chat works in a workspace, a folder whose files the model may read and change. When something you added stops Delorun from starting, safe mode starts it without your plugins until you fix it.
Contents
- Start, open and stop
- Check the release and your setup
- Workspaces and what the model may change
- Make Delorun yours
- Safe mode and recovery
- Trash, export and import
- The plugin and headless commands
- Next
- For the technically curious
Start, open and stop
| Command | What it does |
|---|---|
delorun | Starts Delorun and opens the studio. On a new home it runs setup first (Install and first run). |
delorun start | Starts Delorun without opening the studio. --open also opens it. |
delorun start --foreground | Runs Delorun in this terminal. Ctrl-C stops it. |
delorun open | Opens the studio in your browser with a link that signs in once. --print prints the link instead (A computer without a browser). |
delorun status | Shows the home, the profile, whether Delorun runs, its process, the running and previous release, running chats and the studio's address. --json prints it as JSON. |
delorun stop | Stops Delorun once running chats end their turns. |
delorun stop --now | Stops at once. It cancels running turns and background jobs. |
delorun and delorun start run Delorun in the background, so it keeps running after you close the terminal, unless you answered No to the background question under More settings in setup. delorun setup background asks it again. A background start prints Delorun is running in the background for the profile default (process <pid>) at <address>, then how to see, follow and stop it.
delorun stop stops new turns, prints Waiting for N running chat(s) to end…, and waits up to 30 minutes before it stops anyway. When it is done it prints Delorun stopped for the profile default. delorun stop --now cancels the running chats instead.
Most commands take --profile <name> after their name to act on another profile, such as delorun status --profile work. DELORUN_PROFILE sets it for every command (Your Delorun home).
Edge cases
- If Delorun already runs, then
delorun startsays so and changes nothing. Open it withdelorun open. - If a command needs Delorun running and it is not, then the command exits with code 3. Start it with
delorun start. Exit codes: 0 done, 1 failed, 2 wrong command line, 3 not running (Troubleshooting). - If
delorun startends withthe home process exited with code 1 before it was running; see its log, then readdelorun logs, and rundelorun doctor. A busy studio port shows asfail port(Starting and stopping). - If
delorun stop --nowcannot end the process, then it stops it with a signal and warns that commands it started may still be running. - If you run a
delorun trash,exportorimportcommand while Delorun runs, then it refuses and asks you to rundelorun stopfirst.
Go further
- Run a second profile beside the first with
delorun --profile work(Your Delorun home). - Keep Delorun in a terminal instead of the background with
delorun setup background. - Reach the studio from your phone: Reach the studio from your phone. The commands are
delorun reachanddelorun devices.
Check the release and your setup
delorun doctorchecks your home's permissions, whether Docker answers, the format of your DeepSeek key (without sending it), whether the studio's port is free, on Linux whether bubblewrap can sandbox commands, the last release-log check and the last update check. Each line starts withpass,warnorfail. It exits with 1 when a check fails; it also reports your changes and your CLI profile's plugins.delorun verifychecks the installed release against its signed manifest and the public release log. It runs two checks, the release signature and the installed files, and lists the others asnot run. Its report ends withthis is not a full verification of this Delorun.delorun logsprints where each log is and the recent records of the running Delorun (Where Delorun keeps its logs).delorun --versionprints the Delorun version and the DeepSeek Harness version it runs on.
Edge cases
- If
doctorshowswarn key, then no DeepSeek key is set. Rundelorun setup key, or setDEEPSEEK_API_KEY. - If
doctorshowswarn release-log, then no release-log check is recorded yet. Rundelorun verify. - If you run from a source checkout, then
doctorreports that it checks no release channel. - If
verifyruns offline, then add--offlineto skip the online log check. The checks run as you, so a program running as you could change them.
Go further
delorun verify --release <version> checks another installed release. delorun verify --json and delorun status --json print JSON for scripts.
Workspaces and what the model may change
A workspace is a folder on your computer. Every chat works in one. The workspace's permission preset decides what the commands the model runs may do:
- Workspace Write. The preset every new workspace starts on. Commands run in the sandbox, a fenced area: they may write inside the workspace and the permitted temporary folders. A command that needs more asks you first, and you approve or deny that one command.
- Full access. Commands run outside the sandbox and can write anywhere your user can, without asking.
Commands the model runs in a Workspace Write workspace cannot write under your Delorun home, read its secrets or tokens, or connect to its control sockets, where your system enforces those rules (What Delorun protects).
With setup's default Ask me first, Delorun asks you once for each workspace before it gives it full access. You answer on the computer Delorun runs on: pick Full access in a chat, use Settings → Safety → Permissions, or choose Allow for this chat on an approval card that asks for it (Full access). Other consents ask before the model edits instruction files, adds an MCP server or schedules work (Consents).
Edge cases
- If you choose Ask less (like DeepSeek Harness) in
delorun setup prompts, then a workspace switches to full access as in DeepSeek Harness, after the studio's own confirmation. - If a chat was copied from DeepSeek Harness or another home and ran with full access there, then it opens on Workspace Write. Turn full access on for its workspace again.
- If you pick a folder that Delorun refuses as a workspace, then it names the reason. Refused folders are the filesystem root, your home folder itself, your Delorun home, DeepSeek Harness's home, and a folder that contains either.
- If you use the studio from a phone, then it cannot grant full access (Reach the studio from your phone).
- If you want full access off again, then use Revoke in Settings → Safety → Permissions, pick Workspace Write in a chat, or run
delorun workspace full-access <folder> off.
Go further
delorun workspace full-accesslists the workspaces and their preset.delorun workspace full-access <folder> onshows what full access means and records it after you confirm in the terminal.offwithdraws it without asking.delorun workspace external-agentslists the external agents allowed to start in a workspace without asking. What Delorun protects explains them.delorun mcp list,accept,declineandrevokeanswer MCP server questions from the terminal (MCP servers).- Limit what sandboxed commands can reach on the network in Settings → Safety → Network (Prompt injection and data exfiltration).
Make Delorun yours
Delorun is built to be reshaped. You can change plugin settings, build agent presets, skills and plugins in Creator mode, link your own plugins, or edit Delorun's own files. Delorun records each change to what it runs, so you can see it and undo it. An update carries your changes to the new release or names, before you confirm, any it cannot carry (Updates).
- Where to customise what compares the ways to change Delorun and what each costs at an update.
- Write a plugin for Delorun goes from a new plugin to one that loads in your studio.
- Changing your harness explains what
delorun changesrecords, protection, and undo.
Every change Delorun makes to your profile is also a version of the profile's history, which delorun recover can restore.
Safe mode and recovery
When a plugin or a profile change stops Delorun from starting, or makes it misbehave, start it without your own plugins:
delorun recover safe-mode # the next start leaves out your plugins
delorun start
delorun recover exit-safe-mode # once it works: the next start loads everything againSafe mode leaves out every bundle and plugin you added, including plugins installed from a folder, and keeps DeepSeek Harness's own bundles and Delorun's. It changes no file: your plugins and their settings stay in your profile, and each start in safe mode says what it leaves out. You should see that line at the start.
delorun recover with no subcommand shows where your profile stands: whether safe mode is on, the last update, the profile versions you can restore, and the plugins you ejected or kept disabled.
Edge cases
- If Delorun runs, then stop it first: safe mode takes effect at the next start.
- If you want to remember why, then use
delorun recover safe-mode --reason <text>. - If your profile would run without its protections, for example because its settings turn off the sandbox, then Delorun refuses to start and names the setting and its file. Remove the setting, or start in safe mode (Protections and plugins).
- If you wonder whether Delorun went into safe mode on its own, then it did not: it never turns safe mode on by itself.
Go further
delorun recover restore <version> brings back a saved profile version. delorun recover rollback goes back to the release before the last update (Going back).
Trash, export and import
| Command | What it does |
|---|---|
delorun trash list | Lists deleted chats and workspaces. |
delorun trash restore <id> | Restores a deleted chat. A workspace is restored in the studio. |
delorun trash purge <id>, delorun trash empty | Deletes one item, or every item, forever. |
delorun export <chat-or-workspace> --out <file> | Writes a chat, or a workspace with its chats, as an archive signed by this home. |
delorun import <file> | Checks an archive, shows who signed it and what it holds, and imports it after you confirm. |
These commands change chat data the studio uses, so stop Delorun first. They refuse while it runs.
Edge cases
- If the export file already exists, then
exportdoes not overwrite it. - If the archive would hold something that looks like a secret, then
exportasks first. - If you delete a chat for good, then pieces of it can stay in captured log output. Add
--clear-logstotrash purgeortrash empty(Clearing logs). - If you import an archive from someone else, then the chat shows a banner naming its source. Read it before you trust it (Archives, imports and the trash).
The plugin and headless commands
delorun plugin --profile <name> …runs DeepSeek Harness'sdsh plugininside your Delorun home, so plugins install as in stock. It applies none of Delorun's protections.delorun plugin check <directory>reads a plugin'spackage.json, runs none of its files, and says whether this release would accept the plugin's version ranges.delorun headless …answers one task and exits, asdsh headlessdoes, with Delorun's sandbox protection and guards.
Edge cases
- If a headless task asks for full access, with
--permission-modeor its environment variable, in a folder without a full-access grant, thendelorun headlessrefuses it. Grant full access at this computer first withdelorun workspace full-access <folder> on.
Next
- Keep Delorun current: Updates.
- Choose the model: Model providers.
- Understand the protections: What Delorun protects.
- If something went wrong: Troubleshooting.
For the technically curious
The delorun/docs/contracts/c19-home-process.md defines start, stop, status and their exit codes. The delorun/docs/contracts/c03-update-report.md defines safe mode and delorun recover. The delorun/docs/contracts/c08-archive-and-trash.md defines the trash and archives.
Model providers
The model providers Delorun sets up: DeepSeek, Anthropic, Google Gemini, Groq, Mistral, Moonshot AI, OpenAI, OpenRouter, Together AI, xAI and any OpenAI-compatible endpoint, what each needs, how setup checks its key, and how to change provider later.
Switching from DeepSeek Harness
Switching from stock DeepSeek Harness to Delorun: what delorun import-home and setup copy from ~/.dsh, what you choose one by one, what is held back or stays behind and why, the preview and the dry run, your key, plugins to install afterwards, and going back.