Preface¶

When running long tasks in DSH, ideas and intermediate conclusions often get scattered across the conversation: a requirement noted at the beginning gets lost halfway; to have AI process a note, one has to manually copy the body, specify a directory, and then watch the results. dsh-notes-qiange (Qiange · Smart Notes) is designed to gather these things in one place: the note board opens in the middle column or right sidebar, notes are partitioned by project folders, and they can be dragged into task swimlanes for AI execution, or triggered periodically by schedule.

Below is an introduction to this plugin. It is maintained by jxhsjxhs and is a fork of @zzerx/dsh-plugin-notes (MIT, author 0x7A7A), with project folder partitioning management added on top of the base. It is categorized under Workflows in the community directory and currently has 0 stars. The installation method is source code build only, as it has not yet been published to npm.

What is it¶

One-sentence positioning: A note plugin for DSH, combining a paper card wall note board, project folders, Markdown editor, and task swimlanes. The difference from ordinary note-taking tools lies in the latter part—notes can become tasks, handed over to AI to run in a specified workspace, or triggered periodically by schedule.

To clarify source attribution: The base version is @zzerx/dsh-plugin-notes 0.6.0 (MIT). This branch adds a project (folder) data model, folder filtering, distinction between notes/projects when creating, editor owner dropdown, agent project tools, and WebDAV v2 snapshots with projects. The original project’s MIT license and copyright notice are retained in the repository’s LICENSE.

Installation and Activation¶

It has not yet been published to npm, so we build from source first. The commands below are from the original README; replace <你的 profile 名> with your own profile name:

git clone https://github.com/jxhsjxhs/dsh-notes-qiange.git
cd dsh-notes-qiange
npm install
npm run build

dsh plugin --profile <Your profile name> add "$(pwd)"

This step compiles the plugin artifact locally and installs it into the specified profile. After installation, a note icon appears in the sidebar (only the icon remains when the sidebar is collapsed). Click it to open the note board; click the X or Esc in the top-right corner of the board to return to the session.

After publishing to npm, you can install it directly. The command also comes from the README:

dsh plugin --profile <Your profile name> add dsh-notes-qiange

After activation, there are four entry points, all of which can be toggled individually in DSH settings → Notes → Entry. They are all on by default: the icon at the top of the sidebar (click the row to open the board, click (+) to open the quick create only), the icon at the bottom-left of the input box (three-row menu: New Note / Note Board / Task Swimlane), the “Save as Note” button below each assistant reply (brings the answer, including images, into the quick create floating layer, pre-filling title and body), and the note card on the guide page of the right sidebar. At least one must remain open; if all are closed, the settings page will lock the last open entry, so there will be no deadlock where you cannot open the board. If the host does not have the sidebar installed, selecting “Open in sidebar” will automatically fall back to the middle column.

Core Features¶

1. Project folder partitioning. When creating, you can choose “Note” or “Project”. A project is a folder, and notes are grouped by project. The top folder bar filters “All / Unclassified / [Specific Project]”, supporting rename, color tag change, and delete; deleting a project does not delete the notes, it just moves them back to “Unclassified”. Creating a note while stopped in a specific project automatically places it in that project; the owner can be changed in the editor at any time. The quick create floating layer also has “Note / Project” tabs at the top.

2. Three display modes. Paper card wall / Kanban / Calendar can be switched at any time; the selection is remembered, and project filtering applies to all three views. The six-color paper card color scheme is consistent with Win11 Sticky Notes. Top priority, color can be multi-selected for filtering; title + body real-time search. Archived notes are folded at the bottom of the paper card wall and can be restored / edited / deleted.

3. Due dates and Calendar. Clicking “Due” on a Kanban card selects a date; overdue items are marked red. The calendar is organized by month. Due dates (blue dots), scheduled triggers (green dots, including future repeats), and execution history (orange dots, success/failure) are color-coded. Clicking an item opens the editor.

4. Markdown body. The toolbar covers Bold / Headings / Lists / Checklists / Quote / Code / Link / Table / Undo Redo. Checklists - [ ] display completion badges on the paper card (e.g., 2/5, all checked becomes ✓). In the editor, Ctrl+V pastes clipboard images or ordinary files; they are saved locally to $DSH_HOME/notes-assets/, with only a reference in the body, not stuffing base64 into the note JSON; files appear as “📎 Filename” chips. The right side has permanent buttons 👁 (open with the system default app) and ⬇ (download back).

5. Notes become tasks. Writing the swimlane status turns it into a task. The five-column Kanban (To Plan → To Do → In Progress → Done → Failed) allows dragging to change status. Ordinary notes do not go into the Kanban. The bottom of the editor only keeps a single line of task summary (Status · Workspace · Model · Preset). Clicking “Settings” pulls out an attachment table from the right side of the note; clicking “Collapse” stuffs it back.

6. Execute via AI. Hover over a task card and click “Execute”. The plugin opens a new session in that task’s workspace to run it; the session where the note board is located is not occupied. After completion, the summary returns to the first line of the card, and the full text goes into the “Task & Results” area of the editor. If it runs too long, you can “Reset to To Do”. In the attachment table, you can select the Model and Agent Preset (leaving it empty uses the host default); this only affects the new session dispatched for that task.

7. Scheduled execution. Supports One-time / Interval N minutes / Daily / Weekly (multi-select days) / Monthly. The card displays “Cycle · Next Time”, and the editor displays “Next / Last”. If the host is offline and misses a point for more than 2 hours, it is not retried (cyclic types are deferred to the next cycle, one-time types are disabled and a reason is written), if within 2 hours it is retried once; if the previous round has not finished, the current round is skipped.

8. Edit safety. When editing while a note is paused, it auto-saves to disk after about 1 second; there is a save indicator at the footer. X / “Cancel” / Esc / clicking outside the popup: as long as there are unsaved changes, it pops up “Note has been modified”. You must choose one of: Save and Close, Discard Changes, or Continue Editing. Ctrl+S saves immediately but does not close the popup. Ctrl+Enter or the “Save” button saves and closes.

Typical Usage¶

The flow below is directly given in the “Common Operations” section of the README; follow it in order:

1. The icon at the bottom-left of the input box → Menu “New Project”, first create a directory project to hold code; or click “New Project” in the note board folder bar.
2. Click “New Note” in the same menu, or click (+) in the note icon in the sidebar, to note a “Run the examples in README for scheduled tasks”. During writing, you can use the toolbar “Checklist” (or Ctrl+Shift+9) to insert a few - [ ], Enter to continue line, Tab to indent as a sub-item.
3. Turn this note into a task: Open the editor, select the workspace in the right task attachment table (absolute path, selected from the dropdown, candidates are directories used in recent sessions, only select, do not hand-fill), and write the swimlane status to make it a task. The documentation clearly states: there is no default value and no fallback; if no workspace is selected, it cannot be saved as a task, the summary line turns red, and saving is blocked; task cards in the swimlane without a workspace set display red text “Workspace not set”, and the “Execute” button is also disabled.
4. Drag the card to “In Progress”, hover to click “Execute”, the plugin will open a new session in that workspace to run; after it finishes, look at the summary in the first line of the card and the “Task & Results” area in the editor.
5. If you want periodic checks, set up another scheduled task, e.g., once a day; it will display “Cycle · Next Time” on the card and mark it with a green dot in the calendar view.

Backup via WebDAV: In DSH settings → Notes → Backup, fill in server address, remote directory, account, and app password. It periodically compares by check interval and only uploads snapshots when notes have changed, keeping only the recent retention copies remotely. To verify connectivity immediately, you can click “Save and Backup Now”. Note that images and attachments are not uploaded with the backup; the snapshot only contains the body and notes-asset: / notes-file: references. Restoring on a new machine only restores text and references; if there is no corresponding file on the local machine, the note displays “Image Lost”. Clicking the attachment link will prompt download failure. Before restoring, the plugin will automatically backup the current state first; the selected one will overwrite existing notes in its entirety.

Applicable Scenarios and Notes¶

Suitable for people maintaining long-term projects in DSH: need to hang temporary ideas, requirement items, and AI execution results in a fixed location, and hope that the “Write down -> Turn into task -> AI runs -> Run periodically” chain does not rely on manual copy-paste. Low dependency, almost no need to modify host configuration, install and toggle; the pure UI host can also use the note board normally.

Three points to note. First, the plugin runs with the permissions of the current DSH process and can read/write files and directories the process can access. Before installing, you should read the source code and LICENSE (MIT) to decide; it is built from source, npm install will execute scripts in the repository, and verifying the upstream fork source (@zzerx/dsh-plugin-notes, 0.6.0, author 0x7A7A) is a necessary step. Second, task execution requires explicitly specifying a workspace; there is no default value, select from the dropdown rather than hand-filling the path. Third, if the host has the tools service installed, the plugin registers 8 agent tools (a core set from notes_list, notes_get, notes_list_projects, notes_create_project, notes_create, notes_update, notes_set_pinned, notes_delete, notes_task_set_status, notes_task_report); if the tools are changed or deleted while you are hand-writing notes, it will initiate a “Consent / Reject” request. If the host has no approval channel, the agent can only delete notes it created itself, and task tools are only available within the session authorized for “Execute”.

Development commands in the same repository: npm run typecheck (tsc –noEmit), npm run build (produces lib/index.js + lib/client.js + lib/types), npm run watch (auto-rebuild on src change, host-side changes still require restarting dsh).

Conclusion¶

dsh-notes-qiange shortens the distance between “Write a note” and “Let AI do it”: notes are partitioned by project, tasks and AI execution results fall back onto the same board, and backups can go through WebDAV. If you want to see the interface first, the directory page is https://www.skillhub.cn/plugins/jxhsjxhs/dsh-notes-qiange, and the source code and README are at https://github.com/jxhsjxhs/dsh-notes-qiange.