dsh-plugin-chat-tools

DeepSeek Harness (dsh) plugin for working inside a chat page through a device UI automation bridge: collect the visible conversation once, then read only the delta as new messages arrive.

Companion to dsh-plugin-android-tools. Both plugins talk to the same bridge and share the same contract; this one calls the bridge's read_screen / swipe actions directly, so the core tools plugin does not have to be mounted.

中文说明

Requirements

• dsh running with @deepseek-ai/dsh-tools >= 0.1.0-rc.6 (peer dependency).
• A bridge host reachable over HTTP (same contract as dsh-plugin-android-tools; that README also has a runnable mock host and a host-author checklist).

Tools

Install

# from git, pinned to a release tag:
dsh plugin add github:asdukw/dsh-plugin-chat-tools#v0.2.0

# or from the tarball attached to any GitHub Release:
dsh plugin add ./dsh-plugin-chat-tools-0.2.0.tgz

# once npm publishing is enabled:
dsh plugin add dsh-plugin-chat-tools

The package ships a dsh.bundle layer (cordis.patch.yml) that inserts the plugin row on install. Restart dsh afterwards.

Configure

If either is missing, tool calls fail with ANDROID_BRIDGE_URL/ANDROID_BRIDGE_TOKEN not set.

Usage

Right after entering a chat: call collect_chat once (read + swipe up a few rounds, line-deduplicated), then call read_chat repeatedly to track new messages in place; wait(seconds) pauses client-side between reads. Do not leave or re-enter the conversation while tracking — the seen-line state lives in the plugin process memory and tracks one chat page per task.

Notes

• collect_chat normalizes lines by stripping node refs ([12]) and coordinates (@(x,y)) before deduplicating, so a repeated full-screen read only yields truly new lines.
• Screen text can be personal data; tool results are only returned to the model and are never logged by this plugin.

Development

No dependencies needed for the smoke test (a loader stub replaces @deepseek-ai/dsh-tools):

npm test

Release: push a v* tag. The release workflow runs the tests, packs the package and creates a GitHub Release with the .tgz attached. npm publishing is prepared as a gated job: publish the first version locally (npm login, then npm publish --access public), add a trusted publisher on npmjs.com (package → Settings → Trusted Publisher → GitHub Actions: user asdukw, repository dsh-plugin-chat-tools, workflow filename release.yml, allowed action npm publish), then enable the job:

gh variable set NPM_PUBLISH_READY --body true -R asdukw/dsh-plugin-chat-tools

License

MIT