# [Bug] Sidebar history sessions and workspaces completely lost, and current session has no corresponding entry (Data loss risk) #7637
Replies: 1 comment 1 reply
先说一句要紧的:你的数据大概率没丢——而且"整块都空了"这条线索很关键0. 你那份报告的模板没填正文里还留着占位符: (你写的 1. 所有状态都在一个目录下,先确认你找的是同一个目录DSH 的用户数据根目录由 /** Directory name for the default DeepSeek Harness home under the OS home. */
export const DSH_HOME_DIR_NAME = '.dsh'
/** Environment variable that overrides the default DeepSeek Harness home. */
export const DSH_HOME_ENV = 'DSH_HOME'在这个根下面:存储根是 ⇒ "侧边栏空了 + 工作区也没了 + 重启不恢复"这个组合,最像的解释是:现在跑的这份 dsh 用的不是同一个 home。 请按顺序确认:
2. 先证明数据还在(这一步最重要)直接去看那个根目录: echo "DSH_HOME=${DSH_HOME:-<unset, so ~/.dsh>}"
ls -la ~/.dsh/ # sessions/ storages/ profiles/ ...
ls -la ~/.dsh/sessions/ | head # 每个会话一个目录如果 3. 如果数据确实在同一个 home 里,按这个顺序查
4. 麻烦你补这几条(有了我就能给准确结论)
我不太愿意在没有这些信息的情况下猜"数据被重置了"——从代码看,列表是从磁盘状态推出来的投影,所以"显示为空"和"数据没了"是两件需要分开证实的事,而前者远比后者常见。 |
Uh oh!
There was an error while loading. Please reload this page.
[Bug] Sidebar history sessions and workspaces completely lost, and current session has no corresponding entry (Data loss risk)
🐛 Description
While using DSH, a severe state loss issue occurred:
🖥️ Environment
v0.1.7-rc.1(Modify as needed, e.g., v0.1.5-rc.2 / v0.1.7-alpha.2)🔁 Steps to Reproduce
🎯 Expected Behavior
❌ Actual Behavior
🛠️ Troubleshooting Steps Taken
~/.dshdirectory data files:~/.dsh/sessions/or~/.dsh/profiles/(Confirm whether session data files still physically exist)~/.dsh/workspaces/(Confirm whether workspace data is lost)📝 Additional Context
All reactions