dsh-inbox

dsh-inbox

A local inbox plugin for DeepSeek Harness (dsh): file whatever you copy into one vault, get it back when you need it — including by asking your assistant in conversation.

English | 中文

What it is

The things you copy in a day — a link to read later, a screenshot, a config snippet, an account and password — end up scattered across clipboard history, bookmarks and temp files. dsh-inbox keeps them in one local vault: paste to file, automatic classification, browse and search from the sidebar — and instead of digging through it yourself, ask your assistant "what was that article about caching I saved last month?".

Everything lands on your machine, and the model only sees a record when you ask it to look.

Features

Screenshots

Two ways to use it

① File something from the conversation

/inbox in the composer, followed by text or a link, with images attached right there — this never reaches the model, it only goes into the vault. That is the way to file credentials and throwaway links.

Or just say so — "keep this in my inbox", with the link or the paragraph right there — and the assistant files it for you. That path does put the content in front of the model on the way through, so /inbox stays the way to file credentials.

② Ask for it later

No command, just talk:

which of my saved images is the mini-program code?

show me that article about caching I saved last week

list the links in my inbox I haven't read yet

Two questions in the same conversation, on a real machine:

Install

Needs Node ≥ 22 and a working dsh (the installer brings pnpm along when your machine does not have it). Windows only so far — macOS and Linux are unverified.

Web (command line)

# install (`dsh web` is `dsh --profile web`, so this is the profile you already start)
npx @chance722/dsh-inbox init --profile web --install-pnpm

# never run dsh on this machine? create the profile in the same command
npx @chance722/dsh-inbox init --profile web --create-profile --install-pnpm

# update (within 24h of a release, swap @latest for the exact version, e.g. @0.2.15)
dsh plugin --profile web add @chance722/dsh-inbox@latest

Desktop app (DeepSeek Harness)

Open Plugins in the sidebar → install → enter @chance722/dsh-inbox@latest (within 24h of a release, @0.2.15) → restart when it asks.

That field also takes a GitHub URL (https://github.com/Chance722/dsh-inbox): the built plugin ships in the repository, so it installs the same way with nothing extra to do. Reinstalling is how you upgrade; the package name is still the smoother path day to day.

The same from the desktop's own CLI:

"<desktop install dir>\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop add @chance722/dsh-inbox@latest

Restart afterwards. Inbox is in the left rail, and a new session's assistant can look things up ("what links in my inbox haven't I read yet?").

To keep your daily dsh untouched, give the plugin its own profile and port: npx @chance722/dsh-inbox init --create-profile, then dsh --profile inbox --no-open --port 3102.

Other flags: --profile <name>, --install-pnpm, --no-default, --help.

From a local checkout

git clone <this repo> dsh-inbox ; cd dsh-inbox
pnpm install ; pnpm build
node lib/cli.js init --package <absolute path to this repo>

Uninstall

# 1. remove the package from the profile you installed it into
#    (also drops it from dsh.profile.bundles)
#    desktop app: uninstall it in the Plugins panel — same thing
dsh plugin --profile <that profile> remove @chance722/dsh-inbox

# 2. delete what init created (**dsh 0.1.x only**; from 0.2 init skips this)
rm -r ~/.dsh/.agent-presets/inbox      # the preset copy
# default preset: delete agent-presets.default in ~/.dsh/settings.yaml (falls back to the
# deployment default) or set it to standard; every init left a settings.yaml.bak-* backup

# 3. and the profile itself, if you made one just for this
rm -r ~/.dsh/profiles/<that profile>

Uninstalling does not delete your vault. To remove the records too: rm -r ~/.dsh/storages/dsh_inbox.

Where things live

Everything under %DSH_HOME% (C:\Users\<you>\.dsh on Windows):

What the remote looks like

With a remote configured and /inbox as the directory:

How syncing works

• Automatic: a push seconds after a capture or edit (debounced — several quick saves are one push); 「同步」 is a full sync: push → pull → re-read the list.
• Merging: per id + timestamp, the newer write wins, no conflict copies; needed attachment bytes come down with the record.
• Two machines: one shared 「目录」 (blank, / and inbox are the same). Records a machine left under an older directory come back if you tick Merge other sync directories too in the settings.
• Deleting: 「删除」 only moves a record to the bin and the other devices are told it is gone; emptying the bin deletes the cloud copy as well, and it stays deleted — a copy sitting in another sync directory cannot file it back in.

Privacy and security

• Credential bodies are encrypted at rest (AES-256-GCM, key derived from your master password). Neither the password nor the key is written down: the vault locks on every restart and you unlock it under 设置 → 账密加密, and a forgotten password means unrecoverable ciphertext. With no master password set, a credential is refused rather than stored in the clear. On a second machine, synced credentials open with the master password you set on the first one — the derivation parameters travel, the password does not.
• That covers the body only: notes, categories, tags, timestamps and attachment bytes are not encrypted — a key inside a pasted file is still a key inside a file.
• Masked where it matters: a credential is listed by the name you gave it, and its plain text never reaches a conversation or a model.
• Pictures: classification does send an image to the model, and the conversation gets an [attachment:id] marker — that one image is sent only when you explicitly ask the assistant to look at it.
• The model cannot see your vault unless you ask it to look, and classification requests are redacted first. It can also file what you hand it (see "Two ways to use it"), and a record written that way lands exactly like a paste: no name, credentials still refused while the vault is locked. It files only what you ask it to keep — asking what a link says does not file it.
• Your remote needs access control: only credential bodies are ciphertext up there — text, links, notes and attachment bytes are in the clear, and the master password and key never sync. One extra file, sync/master.json, holds the non-secret derivation parameters (salt, work factors, a check value) so the same master password opens synced credentials on any machine — on a second machine, enter the password you set on the first.
• One thing the install changes outside the panel: reading a link's headline is the plugin's only outbound request (one GET, only for links captured on this machine — pasted, dropped, or handed to the assistant — never for links that came through sync). It goes out with a browser-shaped identity, an override of web-fetch-http.userAgent shipped in this package's cordis.patch.yml. That identity is the whole profile's, the model's own web tools included; your own cordis.patch.yml overrides it. Details: docs/help/link-title-fetch.md.

Development

pnpm install
pnpm build        # lib/index.js (host) + lib/client.js (panel) + lib/cli.js (init) + lib/types
pnpm typecheck
pnpm test         # vitest

Client-side changes need pnpm build (dsh's client-hmr reloads the page); host-side changes need a restart. Details in docs/help/dev-setup.md, milestones in the development bus.

To switch the profile you actually run between the published package and this checkout (default profile web; set DSH_PROFILE for another):

pnpm dev:status    # which one is in use right now
pnpm dev:npm       # point it at the published version
pnpm dev:local     # point it back here (builds first, then links)

License

MIT