Show and tell: driving Cherry Studio agents from DeepSeek Harness (independent remote-access client)

[SAXEM1997]

Hi — I built dsh-cherry-bridge, a DSH (DeepSeek Harness) plugin that pairs with a Cherry Studio desktop over the official remote-access protocol and exposes it as 14 tools inside a DSH session.

It is an independent client: MIT, no fork, no telemetry, not affiliated with Cherry. It speaks @cherrystudio/remote-protocol over the same WebSocket + Noise XX channel the mobile app uses, and pairing is the normal QR flow.

The settings page (part of the plugin): pairing + workspace scope on the left, the paired device on the right.

What a round trip looks like (IDs redacted):

cherry_devices                      -> dev-A  connected
cherry_agents {device:"dev-A"}      -> agentId
cherry_sessions {agentId}           -> sessionId
cherry_send {sessionId, text:"..."} -> terminal state + assistant text
cherry_interactions {sessionId}     -> pending cards; cherry_respond answers

The point is not a new UI. It is that a DSH agent can use a Cherry desktop as the agent host without switching apps: read history, send, wait for a terminal state, answer approval/question cards, cancel. Tool visibility is scoped per DSH workspace, and the default is that nobody has them.

Status and limits

• Verified against desktop 2.1.4-2.1.7. Protocol 0.6/0.7 is not verified yet (the next desktop release will carry it); I will chase it.
• Client only: it never runs an agent on the Cherry side and never reads the desktop database.
• No official support. If it breaks, that is my bug, not Cherry's.
• Along the way I filed agent.parts.list / agent.messages.list pages can exceed the 64 KiB record budget and abort the remote connection #21852 (page byte-budget abort, fixed upstream) and agent.*.list byte budget: an item that cannot fit makes the rest of the list permanently unreachable #21951 (remaining cursor dead-end, still open). Exercising the protocol from a second client turned out to be a decent way to find edge cases.

Install: npx @deepseek-ai/dsh plugin --profile web add dsh-cherry-bridge@0.1.10

Feedback welcome - especially from anyone running remote access behind a reverse proxy or on a non-default port.