前言之翻译? Wait no, final should be translated headings.¶
Need final translated:
Introduction¶
The DeepSeek Harness (DSH) plugin ecosystem emphasizes modularity. As the number of sessions grows during development or debugging, managing them directly through a list becomes inefficient. The dsh-session-folders plugin introduces an independent folder hierarchy for DSH sessions. It does not rely on the core workspace model; instead, it manages session-to-folder mappings through a persistent registry, making it suitable for scenarios that require archiving session memories by directory and isolating project memory.
Core Features¶
Persistent Registry¶
The plugin maintains a standalone DSH storage domain to store folder definitions and mappings from sessionId to folderPath. This data persists after application restarts and does not depend on the core workspace model.
Non-destructive Removal¶
Removing a folder does not delete any session or its log files. Sessions inside a removed folder are automatically returned to the Inbox ('').
Management Interface¶
The plugin provides folder management capabilities on the “Session Folders” settings page:
* Create, rename, or delete folders.
* Archive sessions to a specified folder.
* Each session list item includes a “Move to folder…” action.
Memory Scope Hooks¶
Folder paths are designed as natural keys for project-scoped memory namespaces. By using assignment[sessionId], you can retrieve the folder path to which a session belongs, enabling directory-based memory isolation (for example, .harvis/memory).
Installation and Activation¶
Run the following command in the terminal to install:
dsh plugin --profile web add github:Harzva/dsh-session-folders
After installation, the plugin automatically loads its persistent registry and client-side UI components.
Typical Usage¶
- Automatic Archiving: Sessions can be automatically assigned to the corresponding folder based on the current working directory (cwd).
- Manual Moving: Select “Move to folder…” from the action menu in the session list to move a session to any other folder.
- Project Memory Isolation: When writing code or handling tasks, use the folder path retrieved from
assignment[sessionId]as context to achieve physical isolation of session memories across different projects.
Notes¶
- Sidebar Limitation: The current version does not provide a “group by folder” tree view in the sidebar.
- Architectural Reason: DSH’s
sidebar.workspacesarea is responsible for the session list and does not provide an embedded slot for adding a folder tree. Therefore, a grouped view must be implemented through a core slot patch or another plugin. This plugin only handles the folder registry and UI management portion. - Memory Keys: Folder paths are natural keys for constructing project-level memory namespaces. This should be considered when integrating other plugins that depend on project memory.
Summary¶
By using a persistent registry and memory scope hooks, this plugin provides basic folder management capabilities for DSH sessions. It is suitable for developers who need to organize sessions and project memory in a structured way. For the complete source code and documentation, refer to the GitHub repository.
Need check if quotes straight vs curly. Fine. But maybe user expects exact Session Folders without quotes? It is UI page, quotes okay. Could avoid curly quotes for consistency: “Session Folders”. Use straight double quotes. But markdown doesn’t care. Original uses 「」. We can use “” or quotes. Better use standard English quotes: “Session Folders” and “Move to folder…”. The ellipsis character maybe preserve.
Need ensure no extra heading. Final only.
Introduction¶
The DeepSeek Harness (DSH) plugin ecosystem emphasizes modularity. As the number of sessions grows during development or debugging, managing them directly through a list becomes inefficient. The dsh-session-folders plugin introduces an independent folder hierarchy for DSH sessions. It does not rely on the core workspace model; instead, it manages session-to-folder mappings through a persistent registry, making it suitable for scenarios that require archiving session memories by directory and isolating project memory.
Core Features¶
Persistent Registry¶
The plugin maintains a standalone DSH storage domain to store folder definitions and mappings from sessionId to folderPath. This data persists after application restarts and does not depend on the core workspace model.
Non-destructive Removal¶
Removing a folder does not delete any session or its log files. Sessions inside a removed folder are automatically returned to the Inbox ('').
Management Interface¶
The plugin provides folder management capabilities on the “Session Folders” settings page:
* Create, rename, or delete folders.
* Archive sessions to a specified folder.
* Each session list item includes a “Move to folder…” action.
Memory Scope Hooks¶
Folder paths are designed as natural keys for project-scoped memory namespaces. By using assignment[sessionId], you can retrieve the folder path to which a session belongs, enabling directory-based memory isolation (for example, .harvis/memory).
Installation and Activation¶
Run the following command in the terminal to install:
dsh plugin --profile web add github:Harzva/dsh-session-folders
After installation, the plugin automatically loads its persistent registry and client-side UI components.
Typical Usage¶
- Automatic Archiving: Sessions can be automatically assigned to the corresponding folder based on the current working directory (cwd).
- Manual Moving: Select “Move to folder…” from the action menu in the session list to move a session to any other folder.
- Project Memory Isolation: When writing code or handling tasks, use the folder path retrieved from
assignment[sessionId]as context to achieve physical isolation of session memories across different projects.
Notes¶
- Sidebar Limitation: The current version does not provide a “group by folder” tree view in the sidebar.
- Architectural Reason: DSH’s
sidebar.workspacesarea is responsible for the session list and does not provide an embedded slot for adding a folder tree. Therefore, a grouped view must be implemented through a core slot patch or another plugin. This plugin only handles the folder registry and UI management portion. - Memory Keys: Folder paths are natural keys for constructing project-level memory namespaces. This should be considered when integrating other plugins that depend on project memory.
Summary¶
By using a persistent registry and memory scope hooks, this plugin provides basic folder management capabilities for DSH sessions. It is suitable for developers who need to organize sessions and project memory in a structured way. For the complete source code and documentation, refer to the GitHub repository.
