Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

Home/Getting started/Config & profiles

$DSH_HOME layout: what must be backed up and what can be lost

Migrating machines, reclaiming disk, or afraid an upgrade will eat your config. Know what each directory holds first.

VerifiedVersion and environmentChecked 2026-11-14
Host version
0.1.2-alpha.5
Measured path
~/.dsh (Windows: C:////Users////<you>////.dsh)
Checked
2026-11-14

Copyable command

cd ~/.dsh && tar -czf ~/dsh-config-$(date +%Y%m%d).tgz profiles skills storages llm-deepseek .credentials.yaml

The sizes below are measured, not estimated. On one machine the directories span three orders of magnitude, which decides the backup strategy by itself.

Directory / fileHoldsMeasuredBack up?
profiles/Profile definitions (cordis.yml, cordis.patch.yml, per-profile node_modules)1 MBYes — this is your config
skills/Installed skills19 MBYes — reinstalling is work
storages/Runtime storage21 MBYes — opaque, but it is state
llm-deepseek/Local model state1 MBRecommended
.credentials.yamlGateway and key referencesa few hundred bytesYes, but keep it out of public backups — it references your keys
sessions/Session history896 MBOptional: keep for records, skip for recovery
attachments/Session attachments275 MBSame, and a big one
dsh-runtimes/Downloaded runtimes314 MBNo — reproducible
cache/Cache43 MBNo — rebuilt on demand
logs/Startup and runtime logs6 MBKeep the last few; this is your only evidence
session-backups/, sessions-archive-big/Session backups and archivesvariesNo

By this table, only tens of megabytes really matter (profiles + skills + storages + credentials). The remaining ~1.5 GB is mostly regenerable.

Minimal backup command

cd ~/.dsh && tar -czf ~/dsh-config-$(date +%Y%m%d).tgz profiles skills storages llm-deepseek .credentials.yaml

This skips sessions and runtimes, so the archive lands in the tens of megabytes. Add sessions if you want history, but first understand why it is 896 MB.

Safe cleanup order

  1. cache and dsh-runtimes first — regenerable, lowest risk.
  2. Then sessions and attachments — the big ones, but gone means gone. Confirm nothing there needs revisiting.
  3. Keep the last few logs; deleting them all leaves you blind next time.
  4. Do not touch profiles, skills, storages, or credentials.
Before a credentials file goes into an archive, ask where that archive will live. Cloud drive, git repo, or sending it to someone to debug — all three hand over the key.

What counts as working

Check every line. All of them pass or the job is not done.

  • profiles/web/cordis.yml lists inside the archive
  • The archive is tens of MB, with sessions not accidentally included
  • The credentials file did not ride along into a public place

Where it fails

Symptom, cause, what to do — written in the order it actually happens.

SymptomCauseWhat to do
The archive is over 1 GBtar picked up sessions or attachmentsList directories explicitly; never tar the whole home
Startup is slower after clearing the cacheCache rebuild costs one slow startFirst start is expected to be slow; the second returns to normal

Sources

Verified means measured here. Compiled means every line carries a source.