Question 1

How does the memory feature of the dsh-jingling plugin work, and how can I review or delete memories?

Accepted Answer

Jingling's memory works on a 'propose-then-confirm' basis: she only remembers what you explicitly confirm and never records silently. You can view the memory list on the Jingling page in DSH at any time, and edit or delete any entry. All memories are stored locally and fully reviewable, keeping privacy under your control.

Question 2

Does dsh-jingling support character card import, and will the imported JSON be executed?

Accepted Answer

Yes. Jingling supports importing character cards in Character Card V2 JSON format. The imported content is treated as text only and never executed as code, so you can safely import third-party character cards without security concerns.

Question 3

How do I build and launch the desktop companion (Sidecar) of dsh-jingling on Windows?

Accepted Answer

If you use the one-click install script, it builds the desktop pet automatically. To build separately, run the build command in the sidecar directory, which produces an exe file. Then click the 'Open Desktop Companion' button on the Jingling page in DSH Web, and the transparent window pet will appear on your desktop.

Question 4

What does permission isolation in dsh-jingling mean, and why do I need to switch to a standard session for actual work?

Accepted Answer

Jingling separates companionship from work: she has no Shell, filesystem, network, or MCP permissions, so she cannot perform actual operations. When you need to do real work, you must switch to a DSH standard session, where you choose the directory and grant authorization, ensuring the companion process never oversteps.

Question 5

Where do I set the sidecarExecutablePath configuration for dsh-jingling, and what is the default value?

Accepted Answer

If you place the Sidecar executable in a non-default location, you can specify sidecarExecutablePath in the DSH configuration to point to it. By default, the one-click install script builds the pet to the sidecar/release directory, and DSH finds it automatically, so no extra configuration is needed.

Question 6

Why does dsh-jingling show 'souldock' in some places? Is it a different product?

Accepted Answer

No. To remain compatible with local configurations from early preview versions, some low-level identifiers (such as plugin ID, RPC path, preset directory) still use 'souldock', but the public name and interface are all Jingling / dsh-jingling. This is just to avoid disturbing your existing local data, not a second product.

dsh-jingling: A Local-First AI Companion Plugin for DeepSeek Harness

yi-111-a/dsh-jingling

How to Install

dsh-jingling Key Features

dsh-jingling Repo Summary

What Does It Do?

Core Features

How to Use This Plugin?

DSH Plugin FAQ