Your Delorun home
English | 中文
Summary
This page tells you where Delorun keeps your data, how to move it, how profiles work, and what to do when Delorun refuses a file because other users can read it. You need nothing first; delorun creates the folder the first time it runs (Install and first run). Delorun keeps everything in one folder, your Delorun home: ~/.delorun, or %USERPROFILE%\.delorun on Windows. Your chats, workspaces, profiles, keys and Delorun's own records all live there. delorun creates it the first time it runs and makes it readable by you alone. Back up that folder and you have backed up Delorun.
Contents
- Where the home is
- The first run
- Profiles
- Your DeepSeek Harness home
- Fixing permissions
- Next
- For the technically curious
Where the home is
To keep the home somewhere else, set DELORUN_HOME:
DELORUN_HOME=~/work/delorun delorunThe path must be absolute or start with ~. delorun refuses your home folder itself, the root of the filesystem, and DeepSeek Harness's home ~/.dsh or any folder inside it, because each of those holds other things Delorun must not mix with its own. delorun status prints the home in use.
The first run
The first delorun on a new home runs setup (Install and first run). After that, delorun starts Delorun in the background and opens the studio in your browser, unless you chose in setup to run it in the terminal. delorun status shows whether it runs, and delorun stop stops it once running chats finish, or at once with delorun stop --now. One Delorun runs per profile: a second start tells you it is already running. Daily use lists every command.
Profiles
A profile is one setup of Delorun: its plugins, their settings and its studio port. Most people need only the one setup creates, default. To use another, pass --profile <name> or set DELORUN_PROFILE:
delorun --profile work # sets up the profile the first time, then starts it
delorun status --profile work # other commands take --profile after their nameA profile name has 1 to 32 lowercase letters, digits, - or _. Delorun refuses desktop, kept for a desktop app's own profile, headless, which delorun headless uses, and Windows device names such as con. All profiles share your chats, workspaces and keys.
Your DeepSeek Harness home
Delorun never changes or moves ~/.dsh. It reads it only when you import from it (Switching from DeepSeek Harness). If you set DSH_HOME for DeepSeek Harness, delorun ignores it and uses your Delorun home, and delorun status tells you so.
delorun plugin works as dsh plugin does, inside your Delorun home, and delorun headless answers one task as dsh headless does, with Delorun's sandbox protection and guards (Daily use).
Fixing permissions
On Linux, your home and Delorun's folders in it must be readable by you alone (mode 700), and its secret files too (mode 600). If another user could read one of them, Delorun refuses to use it and prints the command that fixes it:
Delorun stopped before using /home/you/.delorun/secrets/home-auth/home-key.pem.
Why: SECRET_FILE_MODE: /home/you/.delorun/secrets/home-auth/home-key.pem has mode 0640, which other users can read; it must be 0600
What you can do:
Fix it with: chmod 600 /home/you/.delorun/secrets/home-auth/home-key.pemRun the printed chmod command, then run delorun again. Delorun never changes these permissions for you, so a mistake stays visible. A home, folder or secret file that is a symbolic link, or belongs to another user, is refused too, with no command to fix it: move it away and let delorun create it again. On Windows, Delorun does not check these permissions yet.
Edge cases
- If
DELORUN_HOMEis not an absolute path and does not start with~, thendelorunrefuses it. - If
DELORUN_HOMEnames your home folder, the filesystem root, or~/.dshor a folder inside it, thendelorunrefuses it. - If you set
DSH_HOME, thendelorunignores it anddelorun statussays so. - If a profile name uses capitals, spaces or more than 32 characters, or is
desktop,headlessor a Windows device name such ascon, thendelorunrefuses it. - If another user can read your home or a secret file, then Delorun refuses to use it and prints the
chmodcommand that fixes it (Fixing permissions). - If a file or folder in the home is a symbolic link or belongs to another user, then Delorun refuses it with no command to fix it. Move it away and let
deloruncreate it again. - If you run Delorun on Windows, then it does not check these permissions.
- If two commands change the home at once, then the second refuses with
another process … holds the home lock. Wait, then run it again (Starting and stopping).
Go further
- Keep a work setup apart from a personal one:
delorun --profile work. Profiles share chats, workspaces and keys but keep their own plugins, settings and port. - Keep the whole home somewhere else, such as a larger disk:
DELORUN_HOME=~/work/delorun delorun. - Back up Delorun by copying the home folder while Delorun is stopped (
delorun stop). - Move single chats or workspaces between homes with
delorun exportanddelorun import(Daily use).
Next
- Start and stop Delorun: Daily use.
- Read where logs live: Where Delorun keeps its logs.
- If a file was refused: The home and its files.
For the technically curious
The delorun/docs/contracts/c01-home-layout.md lists every folder and file in the home, its required mode and the error codes; Troubleshooting explains each code.
Import your DeepSeek website chats
Bring the chats you had on chat.deepseek.com into Delorun: exporting them from the website, turning on the chat import plugin, uploading the file, what becomes a chat and what does not.
See what a chat costs
See what a chat costs: turning on the cost meter, reading the figure under the message box and its breakdown, how prices are set and overridden, and what the estimate leaves out.