Introduction¶

The DSH plugin ecosystem emphasizes “everything is a plugin,” and the community directory is an independent site with no official affiliation to DeepSeek / Huaquan. In the writing agent scenario, the common split is: the host-side engine handles project, library, search, and orchestration; the browser-side panel handles display and interaction. A protocol adapter layer is needed between them to avoid exposing generation capabilities and full write operations directly to the client.

dsh-writing-remote is exactly this layer: it exposes the host-side writing engine’s data capabilities to the client panel in the form of Typert remote.

What is this¶

dsh-writing-remote is maintained by x2802490130-prog and serves as the host-side data channel for the DSH writing suite.

It solves the problem of:

• dsh-tool-writing engine runs on the host side, possessing project, library, search, and orchestration capabilities;
• dsh-client-ui-writing panel runs on the client side and needs to read this data for display;
• They interact via the Typert protocol, and the remote package is responsible for adapting the engine capabilities into Remote methods callable by the panel.

The boundary of this package is clear: it provides read-only data and orchestration triggers; all write operations are still completed within the host-side engine, and generation capabilities are not exposed to the client.

Core Features¶

dsh-writing-remote primarily exposes project, library, and search data from the dsh-tool-writing engine, and provides a small number of orchestration trigger methods.

Data Reading¶

The panel can obtain the following content via Remote methods:

These methods target a read-only scenario where “what the panel needs, the remote provides.”

Orchestration Triggers¶

dsh-writing-remote also provides two trigger-style methods:

Please note here: the remote is only responsible for triggering; the actual execution is still completed by the host-side engine.

Method Positioning¶

All Remote methods use projectRoot as the first parameter to locate the novel project.

The panel side typically passes the current workspace as projectRoot, and the host side then instantiates the corresponding engine based on that directory.

Installation and Enablement¶

You can install via the DSH plugin method:

dsh plugin --profile web add dsh-writing-remote

You can also install as an npm package:

npm install dsh-writing-remote

The configuration option is only libraryRoot.

libraryRoot

The default value is:

$DSH_HOME/writing-library

This directory shares the library root with the engine and is used to specify the library location for the dsh-tool-writing engine.

Typical Usage¶

Below is a typical integration process.

1. First, install the remote package:

dsh plugin --profile web add dsh-writing-remote

2. If you need to adjust the library location, configure libraryRoot:

libraryRoot=$DSH_HOME/writing-library

3. When calling Remote methods on the client panel, pass the current novel project directory as projectRoot.

For example:

• View project index: call workspaceIndex
• View project status: call projectStatus
• View chapters: call chaptersList
• Preview single chapter: call chapterText
• Browse settings: call loreList
• Search project content: call projectSearch
• View library: call libraryList
• Search library: call librarySearch
• View evolution: call evolutionList
• View thread graph: call threadGraph
• Trigger chapter-end orchestration: call syncNow
• Trigger skeleton initialization: call scaffoldNow

These calls rely on projectRoot to locate the specific novel project; the panel passes the current workspace.

Applicable Scenarios and Notes¶

dsh-writing-remote is suitable for the following scenarios:

• You already have the dsh-tool-writing writing engine;
• You have the dsh-client-ui-writing client panel;
• You need to view project, chapters, settings, library, search, evolution, and thread graphs in a Web panel;
• You want to expose only read-only data and orchestration triggers to the client, keeping write operations on the host side.

Points to note during use:

• It provides a host-side data channel, not an independent writing engine;
• Read-only data and orchestration triggers; generation and write operations are still completed on the host-side engine;
• The plugin runs with the current dsh process permissions; check the source code and license before installing;
• The license is MIT;
• The community plugin directory is an independent site and should not be understood as an official app store.

Links¶

GitHub:

https://github.com/x2802490130-prog/dsh-writing-remote

Plugin directory link address:

https://www.skillhub.cn/plugins/x2802490130-prog/dsh-writing-remote

This directory page address comes from the plugin link and has not been verified in the captured data for this session.